Skip to main content

Customize email templates

Every notification the platform sends — cycle started, vote needed, check-in, invitation — has an editable template, so the emails can speak your organization's language.

Prerequisites​

  • The Can Customize server permission.

Steps​

  1. Open Admin → Email Management → Email Templates. The table lists every template with its current subject and whether it's been customized.
  2. Select a template to open the editor and change the body in the rich-text editor. Placeholders fill in the specifics of each event — the template variables reference lists what's available per template.
  3. Save. A customized template shows Customized? in the list, and you can revert it to the default at any time from the editor.

Change the subject​

A subject line doesn't live in the template body. Each template has a localization property that supplies its subject, and the editor names it — "Localization property to change the subject of this email" — beside a link to the Localization Properties page. Create a property with that key, give it a value per language, and the subject changes without touching the template.

Reference your own wording​

Any localization property is available in a template as ${string.<key>}, resolved in each recipient's UI language. Quote a key that contains periods: ${string["my.custom.key"]}.

That gives you two things:

  • Text you reuse across templates — a footer, a support address — lives in one place per language instead of being retyped into each template.
  • A property whose key matches one a default template already uses replaces that wording wherever it appears, with no template edit at all.

Give every key an English value. Saving renders the template in English first and refuses to save if a key has no value. Where a missing value should render as nothing, write ${string.myKey!""}.