Skip to main content

​
Read and filter the notifications feed

The notifications page (/notifications, reached from the bell in the top bar) renders your org’s in-app alerts as a virtualised list. Each row is a category icon, a title and body, a relative timestamp, and a severity badge — and rows with an action link open straight into the surface that resolves them (security alerts to your security settings, wallet alerts to billing, delivery alerts to the email module). This page is the operations counterpart to Triage the Notification Center, which covers delivery channels, digests, retention, and the API. Where the delivery toggles live (per-user channel matrix, org webhook sinks) is covered in Configure notification channels. Above the feed, the page also pins Active platform alerts — persistent cross-module issue states (outbound paused, KYC pending, compliance risk, webhook backlog, number document expiry) — so the center is never empty while a real issue is outstanding.

​
Category taxonomy

Every notification has a kind — a closed enum that the page’s filter dropdown mirrors exactly, so a kind can never be invisible to filtering. Each kind renders with a dedicated icon; kinds without a mapping fall back to the severity glyph (info circle, warning triangle, or error octagon), and ultimately to a generic bell, so newly added kinds always render something recognisable.

​
Platform events

​
Security alerts

Security kinds are always shown regardless of your notification preferences — suppressible preferences would let a hijacked session mute the takeover signal.

​
Agent and inbox activity

On rows, severity is tinted across the icon and badge: blue for info, amber for warning, red for error. Rows with warning or error severity also carry an explicit severity pill next to the timestamp.

​
Filters and read state

Three filters combine freely in the Filters card; a Clear control appears whenever any filter is active:
  • Unread only — toggle that narrows the feed to unread rows.
  • Kind — dropdown mirroring the full kind enum. The list is group-ordered (security kinds cluster together, inbox kinds cluster together) rather than alphabetised, matching how you think about what you’re filtering for.
  • Severity — info, warning, or error.
A malformed filter value never errors the page — it is ignored and the feed loads unfiltered.

​
Read, dismiss, retention

  • Mark read — hover a row to reveal its check button, or open the row (opening marks it read). Mark all read in the header clears the badge in one click.
  • Dismiss — hover a user-scoped row to reveal the dismiss control; the row hides immediately and the delete commits after a short undo window (~5s). Org-wide rows show no dismiss control — they expire on their own clock.
  • Retention — rows carrying an expiry timestamp drop out of every list and unread count once it passes; rows without one persist until dismissed.
History loads in cursor-paginated pages with a Load more control. The list is virtualised, so only the visible window of rows mounts in the DOM no matter how many pages you accumulate.

​
Live updates

The page subscribes to the notification live stream, so a new row lands without a refresh and read state stays in sync across open browser tabs. If the live channel hiccups, a poll safety net self-corrects within ~30 seconds — the delivery-tuning mechanics are on Configure notification channels. Security-critical kinds (sign-in from a new IP or device, 2FA changes, password or email change, API key mint/revoke, member-role changes, billing anomalies) always mint a row and always bypass per-category mutes — a hijacked session can’t silence the takeover signal.