Page body
What this page shows
This page is the operator inventory for notification templates. It is the main place to create a new notification template, open the edit flow, inspect the linked email HTML, and switch the linked email-template row on or off.
The route is visually a notifications page, but the row dataset comes from the shared email-template inventory and then filters to rows where notificationId is present.
How the page is organized
The list keeps the same accordion grouping as the email-template inventory. Each section is keyed by the backend template family and then filtered so only notification-linked rows are shown.
For every row, the operator sees:
- linked email-template ID
- internal label
- linked
notificationId - row actions for status toggle, edit, and HTML preview
Important actions
Create: opens the notification create formDownload: exports the shared email-template dataset through the backend CSV branchActivate / Deactivate: toggles the linked email-templateisActiveflagEdit Notification: opens the notification edit form bynotificationIdView Email HTML: opens the linked email-template HTML preview modal
Why operators get confused here
The list is driven by email-template data
Even though the route label is Notifications, the inventory does not call a standalone notifications catalog endpoint. It uses get-all-email-templates and filters rows that already have notificationId.
That is why the first visible identifier is still the email-template ID, not the notification primary key.
Status belongs to the linked email-template row
The row-level activate or deactivate action goes through update-email-template and flips isActive. It is a linked template status, not a direct notification-record status mutation.
Preview shows the linked email shell
The modal preview renders template.templateCode.EN from the linked email-template record. It does not preview the notification JSON content itself.
Known caveats
- The list reuses the shared email-template CSV export. There is no dedicated notifications export flow on this route.
- Edit navigation is notification-specific and uses
/notifications/edit/:notificationId. - Notification statistics routes exist in the backend, but they are not the primary source for this inventory page.
Verification status
- status:
verified_backend - main verified routes:
GET /api/admin/get-all-email-templatesPUT /api/admin/update-email-templateGET /api/admin/notifications/:notificationId