Page body
What this page shows
This route is the main inventory for email templates. Operators use it to review template families, open the edit flow, export the catalog, preview stored HTML, and switch activation state.
The page also shows an Untranslated Email Templates Stats block above the main list so operators can spot translation gaps before opening individual rows.
How the page is organized
The main list is grouped by template family. Each accordion title comes from the backend template order list, and each open group contains the rows for that family.
For every row, the page shows:
- internal template ID
- template label
- row actions for activation, edit, and HTML preview
Important actions
Create: opens the create template formDownload: exports the current template dataset through the backend CSV branchActivate / Deactivate Email: toggles theisActiveflag on the selected templateEdit: opens the template edit screenView: opens a modal HTML preview for the currently stored body
Why operators get confused here
Preview is frontend-only
The View action does not call a backend preview route. It opens a frontend modal and renders the stored HTML body for the currently selected language tab.
That means preview is useful for quick inspection, but it is not the same thing as a fully delivered email.
Test send is not on the list page
Operators sometimes expect View to also prove delivery. It does not. Delivery testing happens in the edit screen through Send test email.
Notifications share the same FE component
The same component can switch to a Notifications tab, but the dedicated /notifications route documents that behavior separately. For the email-templates list itself, the primary status toggle uses isActive.
Known caveats
Untranslated Email Templates Statsis present on the route, but this slice verifies the main list, save, test-send, and status flows first.- Preview applies current casino settings substitutions in the frontend before rendering the modal.
Verification status
- status:
verified_backend - main verified routes:
GET /api/admin/get-all-email-templatesPUT /api/admin/update-email-templateGET /api/admin/get-all-email-templates?csvDownload=true