Prepare a message template

Use E-mail Templates for the selected publication's email content. You need editing permission, approved copy and a publication owner who can confirm which message flows use the template.

Confirm the purpose before editing

The ordinary email-template list and editor operate on the current publication's records. A template can be referenced by more than one automation in that publication. Confirm the intended record and its consumers before changing existing content.

The list's Used check means an automation relationship references the template. It is not a sent-message count or a complete explanation of every consumer. It also does not mean the referencing rule is active.

Saving changes to a linked template can affect later message generation, including work already queued but not yet rendered. Agree those effects with the owner before editing a used template. Do not assume a name or default-looking record identifies the safe one to change.

Prepare a new template

1. Confirm the publication and open E-mail Templates.
2. Click Add new email template.
3. Enter Name, Subject and HTML for the agreed purpose.
4. Inspect the Preview pane, then review the copy and the intended consumers with the owner.
5. Click Save, return to the list and reopen the saved record to inspect its content.

A fictional example uses Name “City Journal notice” and Subject “City Journal update”, with this simple HTML:

<p>Hello from City Journal.</p>

This example contains no recipient data, secret links or automatic personalization. Creating it does not select it for an automation or send a message.

Understand Preview and variables

Preview displays the HTML entered in the editor. It does not render the server's actual message context, replace its variables or establish how every email client will display the result.

The message renderer supports Volt expressions such as {{User.first_name}} when the sending context supplies a User. Available values depend on the workflow.

Keep this example plain. Before adding personalization, ask the integration owner which values the workflow supplies and how missing values are handled.

Know what Save changes

The email form saves content directly; it does not provide a separate draft, version or publish control. It has no email Type selector: the consuming workflow determines how the template is used.

Saving a template and dispatching mail are separate actions. The event-driven sender reads its linked template when processing a message. Saving does not rewrite already generated message bodies.

Use Review automation and integration settings to inspect a consuming rule. Use Find and understand message records for the stored mail state.