Lightning Email Templates are the modern email-template system — records (not Setup metadata), share-able like any record, used by Lightning Email Composer in the Activity tab. They replaced Classic Email Templates for most modern email workflows but the two still coexist.
- Open the Email Templates tab
App Launcher → Email Templates. (Lightning Email Templates are stored as records, distinct from Setup-managed Classic templates.)
- Click New Email Template
Top-right.
- Set Name and Related Entity Type
Related Entity Type drives which merge fields are available — Contact / Lead / Opportunity / etc.
- Set Subject
Use merge fields with triple-brace syntax: {{{Recipient.FirstName}}}.
- Compose the Body
Rich text editor with HTML support. Insert merge fields via the picker.
- (Optional) Add Letterhead and Folder
Letterhead applies branding (logo, footer). Folder controls who can see the template.
- Save
Template is created. It's a record — sharable via folders / records / public link.
- Use from the Lightning Email Composer
On any record, open the Activity composer → Email → Insert Template → pick this template.
Which object's fields are mergeable. Account / Contact / Lead / Opportunity / etc.
Optional brand wrapper — header logo, footer disclaimer.
Where the template lives. Folder permissions gate access.
Different objects, different syntax — Lightning uses {{{...}}}, Classic uses {!...}.
- Lightning Email Templates use Handlebars-style merge fields ({{{Recipient.Name}}}). Classic templates use Visualforce-style ({!Contact.Name}). Don't copy-paste between them.
- Lightning templates only work in the Lightning Email Composer. They don't show up in Apex SingleEmailMessage by default — those need Classic templates.
- Folders gate visibility but not edit permission. Anyone with Read on the folder can see; edit requires the user to own the template or have admin access.