Notification Channels
Guardian delivers alerts two ways: the in-app notification bell, and external channels configured in Settings.
In-app notifications
Section titled “In-app notifications”The bell icon in the dashboard header has two tabs:
- Account — saved notices about your account, such as a trial ending or a subscription ending. These are kept on the server, shown with an unread dot, and refreshed every 30 seconds. Click Mark all read to clear the unread count. Clicking a notice opens the related screen.
- Live activity — new alerts, incidents and pending-action approvals, pushed to your browser the moment they happen. This list covers the current browser session only: it is not stored and is cleared on reload. Use Alerts and Incidents for the full record.
Each live item shows its severity (Critical, High, Warning or Info) as a label as well as a colour. A Critical event also shows a brief pop-up message; other events only update the bell’s count, so the screen is never taken over. The bell announces its unread count to screen readers, opens and closes with the keyboard, and Esc closes it.
If the notification list can’t be refreshed, the bell keeps showing the last loaded list and says how old it is, instead of showing an error.
Connection indicator
Section titled “Connection indicator”Next to the bell, a small badge shows the state of the live update connection: Live, Connecting, Reconnecting, Live paused (the connection dropped and Guardian is retrying automatically), or Offline (your device has no network). When live updates are paused, the sidebar counts and screens that refresh on a timer still update.
External delivery channels
Section titled “External delivery channels”Configured under Settings → Notifications and Settings → Email / SMTP:
| Channel | Setup |
|---|---|
| Configure any SMTP provider directly in the dashboard (with presets for Gmail, Outlook/M365, Amazon SES, Mailgun, and Brevo), or use Resend as the delivery provider. Add one or more recipient addresses. | |
| Slack | Configure your own Incoming Webhook URL directly in the dashboard. If you don’t set one, alerts fall back to the platform’s default Slack destination when one is configured. |
| Telegram | Configure your own bot token and chat ID directly in the dashboard. Falls back to the platform default if you don’t set one. |
| WhatsApp Business | Configure your own phone number ID, access token, and recipient directly in the dashboard. Falls back to the platform default if you don’t set one. |
Each configured channel shows an Active / Not configured status and a Send test button so you can confirm delivery is working before relying on it.
Email, Slack, Telegram, and WhatsApp can all be fully configured and updated from the Settings page by a Superadmin. PagerDuty is also configurable from Settings, but only delivers incident escalations — unacknowledged incidents, not regular alerts — and requires the Enterprise plan.
How delivery behaves
Section titled “How delivery behaves”- If several alerts fire for the same device within a short window, Guardian groups them into a single digest notification instead of sending one per alert.
- Failed deliveries are retried automatically with increasing delays before being given up on.
Related pages
Section titled “Related pages”Channels determine where an alert or incident update reaches your team. Manage recipients and provider credentials from Settings.