The job of this console
Keep family coverage complete, preview a template as the recipient will see it, then publish. Fix a bad subject here rather than editing a workflow graph.
Admin · Communications
Notification Templates
Maintain subject lines, bodies, and channel settings for workspace notifications — with preview before publish.
Scroll to Flowcharts. Scenario: Configure workspace notification templates.
The words the product sends
Subject, body, and channel — preview before publish
Notification templates are the subject lines, bodies, and channel settings for workspace notifications. Workflows and approvals send these copies; they do not invent a second message store.
Admin → Notification templates
Route
/admin/notification-templates
Org flag notificationTemplatesEnabled
HR Admin · Org Admin
Seat at the table
Administrators who own communications. Employees only receive the mail. Developers do not hard-code copy when a template family exists.
The working rhythm
Filter by family, open a template, edit, preview, publish. Check dispatch readiness if a family has gaps. Coordinate with Workflow studio so a rule still points at a live template.
Moments that bring you here
A leave approval mail still names the old company. A new automation needs a template that does not exist yet. After a brand change. When a family shows incomplete coverage on the catalog slice.
ⓘ
Templates are copy, not events
The event still comes from leave, timesheet, ticket, or workflow. Changing a template never creates or deletes those records.
Flowcharts
1 — Edit and preview a template
Find a template, adjust copy, preview, then save.
flowchart TD
A[Open templates] --> B[Filter by source/channel]
B --> C[Open drawer]
C --> D[Edit subject/body]
D --> E[Preview]
E --> F[Save]
F --> G[Events use new copy]
- 1Open templatesAdmin → Notification templates.
- 2FilterSource (system/custom) and channel (email/in-app) narrow the register.
- 3Edit in drawerUpdate subject, body, and placeholders carefully.
- 4PreviewRender sample HTML before saving.
- 5SaveSubsequent events pick up the new template.
Overview
Templates control outbound messaging for workspace events (approvals, notifications, and related workflows). System templates ship with the product; custom templates and overrides depend on org configuration.
How to use
1. Prefer overrides over forks
Adjust the existing event template when possible so keys stay aligned with the backend.
2. Keep placeholders intact
Do not rename merge fields unless the event contract supports them.
3. Preview every change
Broken HTML or empty subjects are the most common failures.
4. Test with a real event
Trigger a sandbox approval or notification after saving.