Notifications
What it does
Notifications let administrators manage templates, events, deliveries, and subscriptions for channels such as email or SMS. Templates define content; events record what was triggered; subscriptions control who receives which kinds of messages. An emergency review queue may be available for sensitive notification paths.
Where to find it
- Notifications —
/notifications - Templates —
/notifications/templates - Events —
/notifications/events - Subscriptions —
/notifications/subscriptions - Emergency review —
/notifications/emergency-review
📸 Screenshot: notifications admin (
notifications-admin).
Common tasks
Manage a template
- Open Notifications → Templates.
- Create or open a template: code, channel, body/variables your site uses.
- Save. Voided templates cannot be used for new deliveries.
Review events and deliveries
- Open Events.
- Open an event to see delivery attempts. Failed provider attempts remain in history so nothing is silently lost.
Configure subscriptions
- Open Subscriptions.
- Create a subscription for a user/person, channel, and template or event-type scope.
- Deactivate subscriptions that should stop receiving traffic.
Emergency review
Open Emergency review when your deployment uses moderated / break-glass notification paths, and process items according to local policy.
Tips & limitations
- Real email/SMS providers are configured by operations (SMTP / SMS gateway). Local and CI environments often use a simulated provider — messages appear as deliveries without leaving the platform.
- Subscription admin against a live API depends on notification-subscription endpoints (M10-009 / FE-104). If save fails while other notification screens work, that slice may still be mock-backed.
- Never put secrets or full PHI into template codes or unrestricted variables.