> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/content-designers/search-forms-and-email/email-templates.md).

# Email Templates

A site sends more emails than people expect: account activation, password resets, account blocked or cancelled, form notifications and confirmations. Varbase manages them with **Easy Email**, which gives each type of email a branded template.

## The Templates

Go to **Structure** \ ***Email templates*** (`/admin/structure/email-templates/templates`) to see them: **Default**, **User: Account Activation**, **User: Account Blocked**, **User: Account Canceled**, **User: Password Recovery**, the **User: Created** variants, and more.

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-56308d1c350bf75179a70d3ceb79bcd8a6f8508d%2Flearn-17-email-templates.png?alt=media" alt="The Email templates page listing Default, User: Account Activation, User: Account Blocked, User: Account Canceled, User: Created variants and User: Password Recovery, each with an Edit template button"><figcaption><p>Email Templates</p></figcaption></figure>

## Editing a Template

1. Click **Edit template** next to an email type.
2. Edit the subject and the body like content. Placeholders insert details such as the person's name, the site name and the one-time link.
3. Write in the organisation's voice, and translate the template into each language: account emails follow the person's language.
4. Save, then trigger the email on a test site and check it in the test mailbox.

The **Overrides** tab makes emails from other parts of the site, such as forms or modules, use the same look and sending setup; on a new site it lists the **Default** and **User** overrides. The email theme, with the logo and colours, is on the **Theme settings** tab. It is separate from the website theme because email programs display design differently; include it in the brand work.

## Scenario: "I Never Got the Password Reset"

1. Open **Reports** \ ***Email log*** (`/admin/reports/email`). Its **Recipients**, **Created**, **Sent** and **Status** columns show who each email was for, when it was created and sent, and whether it succeeded. It holds email addresses, so access is limited to administrators.
2. If it was sent, ask the person to check spam, and ask the client's IT team whether the domain authorises the site to send email.
3. If it was not sent, ask the development team to check the mail service on that server.

## Testing Safely

On development and staging sites, emails must never reach real people by accident. Those sites catch every outgoing email in a test mailbox. Test each email in each language there before launch.

## Planning Notes

* Choose the sending service and sender address, and have the client's IT team add the domain records that authorise the site to send. The development team sets the service up under **Configuration** \ **System** \ ***Mail System*** (`/admin/config/system/mailsystem`) and the email transport settings, which hold the service's credentials: keep them off screen.
* Ask the development team for a list of every email the site can send; agree wording and languages for each.
* Editor notifications, such as a post waiting for review, are not on by default; they can be added with the automation tools.
* Developers: see [Easy Email Recipes](https://docs.varbase.vardot.com/developers/understanding-varbase/easy-email-recipes.md).
