# Notification Providers Notification delivery is performed server-side, so the dashboard does not need to remain open in a browser for notifications to be sent. Notification delivery is intentionally isolated from telemetry collection and alert storage. A failed notification request does not stop telemetry collection or prevent the alert event from being stored. Multiple notification providers can be configured from the **Notification Settings** panel on the **Alerts & Notifications** page. ## Discord Discord notifications are delivered using a Discord webhook. To enable Discord notifications: 1. Create a webhook for the desired Discord channel. 2. Open the **Alerts & Notifications** page. 3. Enter the Discord webhook URL. 4. Enable Discord notifications. 5. Save the settings. Alert notifications include the alert severity and message, along with the affected metric when applicable. ## ntfy ntfy notifications can be delivered through the public ntfy service or a compatible self-hosted ntfy server. To enable ntfy notifications: 1. Open the **Alerts & Notifications** page. 2. Enter the ntfy server URL. The default public server is `https://ntfy.sh`. 3. Enter the topic that should receive dashboard alerts. 4. Enter an access token if the server or topic requires authentication. The token is optional. 5. Enable ntfy notifications. 6. Save the settings. An ntfy account is not required when using a server or topic that permits unauthenticated publishing. ## Gotify Gotify notifications can be delivered to a Gotify server using an application token. To enable Gotify notifications: 1. Create an application in Gotify and obtain its application token. 2. Open the **Alerts & Notifications** page. 3. Enter the Gotify server URL. 4. Enter the application token. 5. Enable Gotify notifications. 6. Save the settings. The dashboard maps alert severity to Gotify message priority so more important alerts can be presented with a higher priority. ## Pushover Pushover notifications are delivered through the Pushover message API. To enable Pushover notifications: 1. Obtain the Pushover user key for the destination account. 2. Create or select a Pushover application and obtain its API token. 3. Open the **Alerts & Notifications** page. 4. Enter the user key and API token. 5. Enable Pushover notifications. 6. Save the settings. Critical dashboard alerts use Pushover priority `1`. Emergency priority `2` is intentionally not used because it requires retry and expiration parameters and has different acknowledgement behaviour. ## Generic Webhook The Generic Webhook provider sends the complete alert event to a custom HTTP or HTTPS endpoint using an HTTP `POST` request with a JSON body. To enable Generic Webhook notifications: 1. Open the **Alerts & Notifications** page. 2. Enter the destination HTTP or HTTPS URL. 3. Enable Webhook notifications. 4. Save the settings. The request uses the following general structure: { "source": "X-ONU-SFPP Dashboard", "event": { "...": "complete alert event" } } The `event` object contains the alert data generated by the dashboard, which may include fields such as severity, message, metric, previous value, current value, and delta. Generic Webhook endpoints should validate incoming requests as appropriate for the receiving system. ## Email (Gmail SMTP) Email notifications are delivered through Gmail SMTP using implicit TLS on port `465`. To enable Email notifications: 1. Enable 2-Step Verification for the Google account if it is not already enabled. 2. Create a Google App Password for the dashboard. 3. Open the **Alerts & Notifications** page. 4. Enter the Google account email, App Password, and one recipient email address. 5. Enable Email notifications. 6. Save the settings. Use a Google App Password only. Do not enter the normal Google account password. Google Workspace addresses using a custom domain are supported when the account can authenticate through Gmail SMTP. The App Password is stored in the persistent notification configuration. Treat the dashboard's persistent `/data` directory and its backups as sensitive. ## ntfy Topic Security Topics on a public ntfy server should not be treated as private merely because the topic name is difficult to guess. Anyone who knows or discovers an unauthenticated topic name may be able to subscribe to messages published to that topic. Use a sufficiently random topic name and avoid including sensitive information in notifications sent to a public unauthenticated topic. For stronger access control, use an authenticated ntfy configuration or a self-hosted ntfy server and configure an access token when required. ## Private Notification Destinations Gotify, ntfy, and Generic Webhook destinations are restricted to publicly routable IP addresses by default to protect against SSRF. Private or self-hosted destinations must be explicitly allowed by the administrator with `NOTIFICATION_PRIVATE_ORIGINS`, using a comma-separated list of exact origins: NOTIFICATION_PRIVATE_ORIGINS=http://gotify.example.lan:8080,https://ntfy.example.lan Origins are matched by exact scheme, host, and port. Paths and query strings are not allowed. DNS addresses are validated before connecting, connections are pinned to validated addresses, redirects are not followed, and URL-embedded credentials are rejected. Leave `NOTIFICATION_PRIVATE_ORIGINS` unset when all destinations are public. ## Notification Credential Security Discord webhook URLs, Gotify application tokens, Pushover credentials, ntfy access tokens, private Generic Webhook URLs, and Gmail App Passwords should be treated as sensitive configuration. Do not publish notification credentials in screenshots, logs, Git repositories, support posts, or other public locations. Anyone with a Discord webhook URL may be able to post messages to the associated Discord channel. If a Discord webhook URL is accidentally exposed, rotate or delete the webhook and create a new one. If another notification credential or private endpoint is exposed, revoke, rotate, or replace it when supported by the notification service.