🚀 Feature: Security notifications to telegram discord webhook etc. #467

New Issue

OVERLORD · 2026-02-04T20:03:02+03:00

OVERLORD commented

2026-02-04 20:03:02 +03:00

Originally created by @lordraiden on GitHub (Sep 11, 2025).

Feature description

A feature to generate notifications based on some scenarios

user: add delete modify
tokens: add delete
admin: login
permissions: new admin
app/integration: add delete

Pitch

For security reasons a way to be notified about relevant changes in the configuration.

Originally created by @lordraiden on GitHub (Sep 11, 2025). ### Feature description A feature to generate notifications based on some scenarios - user: add delete modify - tokens: add delete - admin: login - permissions: new admin - app/integration: add delete ### Pitch For security reasons a way to be notified about relevant changes in the configuration.

OVERLORD closed this issue

2026-02-04 20:03:10 +03:00

OVERLORD commented

2026-02-04 20:03:18 +03:00

@kmendell commented on GitHub (Sep 11, 2025):

Pocket ID is meant to be soley a OIDC provider, Features like this would bloat the UI with configuration options in order to configure them, and Pocket ID biggest goal is to keep everything simple and to the point. Features like this cabn easily be built around the api for your individual use case.

@kmendell commented on GitHub (Sep 11, 2025): Pocket ID is meant to be soley a OIDC provider, Features like this would bloat the UI with configuration options in order to configure them, and Pocket ID biggest goal is to keep everything simple and to the point. Features like this cabn easily be built around the api for your individual use case.

OVERLORD commented

2026-02-04 20:03:23 +03:00

@lordraiden commented on GitHub (Sep 11, 2025):

Pocket ID is meant to be soley a OIDC provider, Features like this would bloat the UI with configuration options in order to configure them, and Pocket ID biggest goal is to keep everything simple and to the point. Features like this cabn easily be built around the api for your individual use case.

Configuration options? it requires 2 parameters to send notifications to telegram. and the 4 check boxes to select what you want to send...

@lordraiden commented on GitHub (Sep 11, 2025): > Pocket ID is meant to be soley a OIDC provider, Features like this would bloat the UI with configuration options in order to configure them, and Pocket ID biggest goal is to keep everything simple and to the point. Features like this cabn easily be built around the api for your individual use case. Configuration options? it requires 2 parameters to send notifications to telegram. and the 4 check boxes to select what you want to send...

OVERLORD commented

2026-02-04 20:03:41 +03:00

@cdanis commented on GitHub (Dec 1, 2025):

I came here to file a FR for similar functionality.

I understand we don't want to bloat the UI, have to take on maintenance burdens for many different notification services, etc.

But can we instead added support for just one simple outgoing webhook implementation, and then leave it to users or the community to hook that up to actual push notification services?

POSTing the JSON payload of an audit-log event would be simple and sufficient -- exactly what you can poll from the API, only pushed.

(And in the case of common self-hosted push servers like ntfy.sh, this would already be sufficient, along with some basic configuration on the ntfy side.)

@cdanis commented on GitHub (Dec 1, 2025): I came here to file a FR for similar functionality. I understand we don't want to bloat the UI, have to take on maintenance burdens for many different notification services, etc. But can we instead added support for just **one** simple outgoing webhook implementation, and then leave it to users or the community to hook that up to actual push notification services? POSTing the JSON payload of an audit-log event would be simple and sufficient -- exactly what you can poll from the API, only pushed. (And in the case of common self-hosted push servers like ntfy.sh, this would already be sufficient, along with some basic [configuration](https://docs.ntfy.sh/publish/#custom-templates) on the ntfy side.)

OVERLORD commented

2026-02-04 20:03:50 +03:00

@Alfredooe commented on GitHub (Dec 23, 2025):

I'd quite like to see this re-opened if possible @kmendell , happy to work on a PR. I don't think this would add excessive complexity, You could just assume Slack's webhook format which would also integrate with Discord / RocketChat / Mattermost.

@Alfredooe commented on GitHub (Dec 23, 2025): I'd quite like to see this re-opened if possible @kmendell , happy to work on a PR. I don't think this would add excessive complexity, You could just assume Slack's webhook format which would also integrate with Discord / RocketChat / Mattermost.

OVERLORD referenced this issue

2026-02-04 20:54:45 +03:00

[PR #467] [MERGED] chore(translations): update translations via Crowdin #791

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/pocket-id#467