Emails
Templates and themes
Brand base, lifecycle library, saved sections, and style push.
Templates are starting points. They are not a second sending path. A campaign or Journey always sends a confirmed message document; a template only helps you create that document faster.
Where they live
Open Emails → Templates. Two groups:
| Group | What it is |
|---|---|
| Library | Seeded lifecycle layouts (welcome, product, activation, come-back) plus the brand base. Catalog layouts stay editable. |
| Your templates | Layouts your team saved. Deletable. |
Each card shows languages, a preview, and Edited. Hover (or tap) for Edit template and Use for email.
Brand base
The brand base is the default scaffold for New email when you do not pick another template. It carries your logo, type, colors, and footer shape. It is editable but not deletable — every project needs a place new mail can start from.
Changing the brand base does not rewrite confirmed emails. Those keep the style snapshot they were confirmed with.
Using a template for an email
Use for email creates a new library email from that layout, then opens the editor. From there it is a normal document: draft, test, confirm. Attach it to a campaign or copy it into a Journey step later.
New email in Content can also start from any active template.
Themes (Design styles)
A theme is a named emailStyle you can save and reuse (colors, type, spacing, logo width). From Design you can:
- Save the current look as a theme
- Apply a saved theme to the open draft
- Push a theme onto other proposed drafts and active templates
Confirmed mail stays frozen. Push is for drafts and templates, not for rewriting history.
Foundation’s brand kit is the visual source of truth the first time a project is set up. Templates can diverge after that; usesCurrentBrand on a template tells you whether it still tracks the kit.
Saved sections
Inside the editor, save a fragment (for example a three-up feature row) as a saved section. Other emails can insert it. Pushing an update rewrites every usage still linked to that section — check the usage list first.
Library vs Journey copies
Duplicating from the Emails list sets copiedFromId so the card can say “Copied from library”. Journeys that reference an existing document do not fork it. Copy-into-journey is explicit so the step can evolve without changing the library original.