Notifications
Configure messenger alerts, webhook-failure alerts, and security alerts from the dashboard Settings page via notification preferences.
The dashboard’s Settings → Notifications page controls which alerts PrivacyFlow sends you and over which channel. Three categories: messenger alerts, webhook alerts, and security alerts.
Open notification preferences
- Sign in to the dashboard.
- Open Settings (top-right gear, or the sidebar entry).
- Open the Notifications tab.
Warning
Screenshot placeholder — Settings → Notifications tab with three toggle rows: messenger alerts, webhook alerts, security alerts.
Three categories
Messenger alerts
Per-messenger toggles (Signal / SimpleX / Session). When on, PrivacyFlow sends you an alert on that messenger when something noteworthy happens on the same messenger — for example, an inbound message that bounced because the recipient blocked the bot, or a delivery failure.
Webhook alerts
When your webhook delivery starts failing (your receiver returns non-2xx, or the request times out), PrivacyFlow can alert you on a messenger of your choice so you don’t silently miss messages. One row in the settings reads “Receive immediate alerts if your webhook fails to deliver.”
Security alerts
Suspicious-login or credential-abuse detection alerts. Enabled or disabled as a category. Recommended on.
How alerts reach you
Each alert setting routes to whichever messengers you have connected. If you only have Signal connected, alerts go to Signal; if you have all three, the dashboard picks based on per-alert routing rules (typically: alerts about messenger X go to messenger X).
Note
Notification preferences are stored on the backend (/dashboard/notification-preferences) and read on every dashboard load. Toggling a preference flips it immediately — no restart required.
Per-app webhook alerts
The webhook auth wizard sets auth per app; the notification preferences set whether you get told when that auth fails. If you have multiple apps with webhooks, a single global setting covers all of them — the alert names the app that failed so you know which one to fix.
Underlying API calls
| UI action | API route |
|---|---|
| Open Settings → Notifications tab (loads current toggles) | GET /dashboard/api/dashboard/notification-preferences |
| Toggle a category on/off → save | POST /dashboard/api/dashboard/notification-preferences with the full updated preferences object |
The dashboard proxy forwards to /dashboard/notification-preferences on the backend. The endpoint exists so the dashboard renders toggles from a single source of truth rather than caching them client-side. See the account API reference.