Page body
What this module is for
Use Notifications to manage the operator-facing templates that power inbox, system, personal, or broadcast notifications.
The module is split across two linked records:
- the notification record itself, which stores title, localized content, priority, and delivery semantics
- the linked email-template record, which gives the notification route a reusable HTML shell, preview modal, and row-level status toggle
Operators use this module to:
- review which notification templates already exist
- open the create or edit flow for one notification
- inspect the linked email HTML shell
- switch the linked email-template row on or off
Main surfaces
List: notification inventory built from the shared email-template catalog, filtered down to rows that already havenotificationIdForm: create and edit workflow for one notification template, including localized content, sender avatar, and priority
Known caveats
- The list is not backed by a standalone
notificationscatalog endpoint. It reads the shared email-template dataset fromGET /api/admin/get-all-email-templatesand keeps only rows that already havenotificationId. - The row-level status toggle uses the linked email-template update route and flips
isActive. It does not callPUT /api/admin/notifications/:notificationId. - The preview modal renders the linked email-template HTML in the frontend. It is not a backend preview route for notification JSON content.
- Backend create supports
sendEmail, but the current operator form does not expose a send or preview-send action.