February 14, 2026
To create a Lightning email template in Salesforce, enable Lightning Email Templates in Setup, assign the Access Drag-and-Drop Content Builder permission, then open App Launcher > Email Templates > New Email Template. Save the record, click Edit in Builder, and design the email with drag-and-drop rows, images, buttons, and merge fields. You get a branded, responsive template you can reuse in manual sends, list email, Flow, Email Alerts, and Apex.
Below is the full walkthrough. The setup that unblocks the Builder, each build step, merge field syntax, the limits Salesforce documents, and what to do when the Edit in Builder button never shows up.
Lightning email templates are reusable, branded emails you design and store inside Lightning Experience. They support merge fields, attachments, list email, and Apex. One template can serve a rep, a Flow, and a batch job.
The Email Template Builder is the drag-and-drop editor that creates them. You add headers, columns, images, and buttons on a canvas, and Salesforce writes the responsive HTML for you. For a wider view of how admins use them day to day, this guide to Lightning email templates is a useful companion read.
Salesforce still ships several template types, and the names overlap. Here is the short version.
If you are starting fresh, build in the Email Template Builder. The other types mostly exist for legacy orgs.
Three checks save hours of guessing. Get them right and the Builder simply works.
The Email Template Builder runs in Professional, Enterprise, Unlimited, Performance, and Developer Editions, in Lightning Experience. Turn on enhanced folder sharing for email templates so folders can be shared with roles, groups, and territories. Then grant the drag-and-drop permission.
Permission hygiene is where template rollouts usually stall. Clean profiles, permission sets, and folder access are part of steady day-to-day Salesforce administration, not a one-time task.
Six steps take you from a blank org to a tested template. Use the table as your map, then follow the detail below it.
In Setup, use Quick Find to open Lightning Email Templates and enable it, along with folder sharing. Then create a permission set, switch on Access Drag-and-Drop Content Builder under System Permissions, and assign it to yourself and your users.
If the button still hides, log out and back in. Permission changes sometimes need a fresh session.
Open the App Launcher, search Email Templates, and click New Email Template. Enter a clear name, pick a folder, add a subject, and set Related Entity Type to Contact, Lead, or whichever object your merge fields need.
Leave the HTML Value field empty. Paste HTML there and Salesforce treats the record as a custom HTML template, which locks the Builder out for good.
Save the record, then click Edit in Builder. The canvas opens with a component sidebar on the left and a settings panel on the right.
Set the page background, content width, and padding first. Every component you drop in then inherits the same frame. If you want guided practice, the Trailhead modules on email templates walk through the canvas at your own pace.
Drag rows in first, then drop content inside them. These are the components you will reach for most.
Click into a Rich Text component and choose the merge field icon. Pick the source — Recipient, Sender, Organization, or the related record — then choose the field, such as First Name. Salesforce inserts a placeholder that resolves per recipient at send time.
The subject line has no picker, so type merge fields there by hand. Always set a fallback value for fields that can be blank, or your email opens with "Hi ," in front of a customer.
Never ship a template you have not seen rendered. Save in the Builder, preview it against a real record, and switch between the desktop and mobile views.
Finish with a live test. Open a Contact, go to the Email tab in the Activity panel, click Insert Template, and confirm the layout holds and every merge field fills.
This is where most migrations break. Classic and Lightning use different syntax, so pasted fields fail silently.
Lightning templates use triple curly braces. A Classic field such as {!Contact.FirstName} will not resolve inside a Builder template, so rebuild it with the picker rather than pasting it in.
Cross-object merge fields are also limited. If the data sits two objects away, add a formula field on the related record and merge that field instead.
The Builder trades some control for speed. Salesforce documents the boundaries, and knowing them up front prevents rework.
The lock-in point deserves real attention. Clone a proven template before you test an idea on it. Admin-focused resources such as Salesforce Admins track how these behaviors shift from release to release.
Nine times out of ten, it is permissions. Work down this list before you open a support case.
A template earns its keep when it sends itself. Lightning templates plug into every automation layer on the platform.
In Flow, use the Send Email action and point it at the template. Email Alerts do the same job inside approvals and record-triggered automation. For custom logic, Apex can build a message from the template and swap the recipient or the related record at run time. Wiring templates into those paths is standard work in a Sales Cloud implementation.
Two rules keep this tidy. Use one template per journey stage, and never clone a template just to change a subject line. Set the subject in the automation instead.
Most guides stop at building one template. The harder problem is 200 templates spread across sandboxes and production with no naming standard.
Templates are metadata, so they can ride your deployment pipeline. Retrieve and deploy the EmailTemplate metadata together with the folder that holds it, and check the Salesforce Developers reference for the fields involved. Content assets behind your images have to travel too, or the header breaks in the target org.
Set guardrails early. Use a naming convention that encodes object and purpose, one shared folder tree per team, a review step before any template goes public, and a named owner for retirement. Templates feeding AI-driven personalization need that discipline even more, because one broken merge field scales instantly.
That is the difference between a template library and template sprawl.
Enable Lightning Email Templates in Setup, assign the Access Drag-and-Drop Content Builder permission, then create a template from App Launcher > Email Templates. Save it, click Edit in Builder, and design it with drag-and-drop components.
It is not a separate app. Open a Lightning email template record and click Edit in Builder. That button opens the drag-and-drop canvas.
The most common cause is a missing Access Drag-and-Drop Content Builder permission. The second is an HTML Value entered when the template was created, which locks the record to the HTML editor.
Yes. Lightning templates use triple curly braces, such as {{{Recipient.FirstName}}}, instead of the single-brace syntax Classic uses. Set fallback values for fields that can be blank.
Yes. A Flow Send Email action can reference a Lightning email template, so the right message goes out automatically when a record changes.
Text, Custom HTML, Letterhead, Visualforce, and Lightning templates built in the Email Template Builder. New builds should use the Builder unless you need Visualforce-level logic.
The Email Template Builder takes you from plain text to branded, reusable email in an afternoon. Set the permissions once, design with components and merge fields, then reuse the template everywhere your automation needs it.
Minuscule Technologies is a Salesforce engineering partner. We design template systems, connect them to Flow and Apex, and keep folders, permissions, and deployments clean so every automated email lands on brand. Talk to us about your org, and we will map the fix.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
