Notification templates

Templates format automatically generated messages. Customize the wording for a particular event, channel and locale while keeping the variables that supply each recipient's context. A template is separate from the business action that triggers a notification.

Access needed

Find the correct template

Open Notifications → Templates. Search for the relevant event and inspect Channel, Locale, Source and Variables. One event can have several channel entries; choose the intended row before editing.

Choose an event and channel

FinTrax workspace

Enlarge

Default identifies a built-in template. A workspace override replaces the effective wording for its event, channel and locale. You cannot create an arbitrary new event by inventing a template name.

Review the existing content

Open the template. Check its event name, channel, locale and source, then read Subject, Body and any Plain-text body. The Available variables list identifies the context supported by that event.

Review the effective source

FinTrax workspace

Enlarge

Templates use Liquid source. Variables are placeholders replaced with actual event values when messages are rendered. Preserve their exact spelling and delimiters; use the listed variables instead of hard-coding a person's name, workspace or record link. Ask your template administrator for help when changing formatting or conditional content.

Edit and preview safely

1. Confirm the scope

   Verify the event, channel and locale. Editing an Email entry does not also update its InApp or SMS entry.

2. Make a focused wording change

   Preserve necessary variables and links. Keep the message clear about what happened and what the recipient should do next.

3. Render the sample

   Select Preview sample. Review the rendered subject, body and plain-text alternative where present. Fix rendering errors before saving. Changing a field clears the earlier preview; preview again after your final edit.

4. Save and verify the override

   Review the final source and select Save override. Check the result, reopen the same template/channel/locale and verify the effective content and source. Use Cancel when you do not want to save the draft.

Render sample content

FinTrax workspace

Enlarge

The example renders a timesheet-approved email with fictional sample values. Its workspace name and sample links are illustrative and should not be copied into your template as fixed text.

Respect channel limits

Channel	Content requirements
Email	Required subject, up to 500 characters; body and optional plain-text body up to 100,000 characters each. The shared email layout is a special case.
InApp	Required title/subject up to 200 characters; body up to 2,000 characters; no plain-text alternative.
SMS	Body up to 1,000 characters; no subject or plain-text alternative.

All template parts must be valid Liquid and the body is required. The shared layout.email template wraps email content and must preserve its content placeholder. Review its broader effect before changing it, because it is shared by email messages.

Understand locales

Locales can identify a language or regional variant, such as en or en-GB. Template selection falls back from the full locale to its language and then English. Review the effective entry rather than assuming a similarly named locale has the same override.

Restore the default

When an override exists, Restore defaults removes that workspace override for the selected locale after confirmation, allowing the default/fallback content to apply again. It is unavailable when there is no override to remove. Review the exact event, channel and locale before confirming, then reopen the entry to verify its effective source and wording.

Troubleshooting

Problem	What to check
Templates is unavailable	Reading, previewing, saving and restoring all require notifications.templates.manage.
Preview fails	Check valid Liquid, supported variables and channel requirements; read the error before saving.
A variable renders sample information	Preview intentionally uses sample data; inspect the variable rather than copying its sample value.
A saved edit does not affect another channel	Each channel has its own template entry.
Earlier notifications look unchanged	Overrides affect future rendering, not historical messages.
Restore defaults is disabled	The effective entry has no removable workspace override.
Preview works but delivery fails	Check the separate delivery log and provider setup. Preview does not send.

What was verified

The live template catalogue, default timesheet-approved Email editor and successful sample preview were inspected in light theme. Three screenshots use the shared viewer. No source was edited, override saved, default restored or message sent. Locale fallback and actual recipient rendering were not live-tested.