Emails sent as part of Auth0 workflows each have a corresponding email template which determines the email’s from address, subject, message body, and more. After you configure an external SMTP email provider, you can modify email templates to customize your emails. Content fields in email templates support Liquid, an open-source templating language that extends the functionality of HTML. Liquid lets you:Documentation Index
Fetch the complete documentation index at: https://docs-staging.auth0-mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
- Dynamically populate variables with data, like replacing
{{ user.name }}with the user’s name - Implement logic, like
if/elsestatements - Modify data with filters for string and array manipulation, math operators, and more
Overview
| Read… | To learn… |
|---|---|
| Customize email templates | How to customize email templates |
| Supported Liquid syntax | About Liquid syntax (tags, filters, and variables) supported in email templates |
Available email templates
The following is a summary of available email templates:| Email template name | Sent when… | Contains… |
|---|---|---|
| Blocked account email | Access to an account from a specific IP address is blocked by brute-force protection. | A link to re-enable the origin of the request. |
| Change password code email | A user requests a password change | A link to the password reset page and a code to use on that page. |
| Change password link email | A user requests a password change | A link to the password reset page. |
| MFA enrollment email | An admin sends an Auth0 Guardian MFA enrollment invitation. | A link that shows the MFA enrollment experience. |
| MFA verification code email | A user using a MFA email verifier needs a MFA verification code | An MFA verification code |
| Password breach alert email | Auth0 detects that the user is trying to access the application with a password that has been leaked by a third party | Informational content |
| Passwordless OTP email | A user logs in with email authentication | |
| User invitation email | A user is invited to an organization or application | A link to join the organization |
| Verification code email | You have enabled code-based verification and a user signs up or logs in for the first time, or you have enabled the Adaptive MFA policy and there is a low-confidence transaction for which account ownership must be verified | A code that the user needs to enter during authentication |
| Verification link email | A user signs up or logs in for the first time | A link to verify the user’s email |
| Welcome email | The user verifies their email address (if this template is enabled), or when the user signs up or logs in for the first time (if disabled) | Informational content |
Email template limits
- Email template customization is not available when using the built-in email provider. To use email templates, configure an external SMTP email provider.
- Each type of email has exactly one template. You can use Liquid to implement conditionals and other logic for use cases like multilingual emails.
- Email templates do not support plain text emails. All emails must be HTML.
-
In the MFA enrollment email template, the
connection.namevariable is not available. -
In the Passwordless OTP email template, only the
emailproperty of theuserobject is available. - Unlike other email templates, the Passwordless OTP email template is configured on the Passwordless Connections email settings page rather than the Email Templates page.
-
For security purposes, the From Address in email templates may not contain
@auth0.com. If you enter an@auth0.comemail address in From Addresses, your tenant sends only default emails, ignoring any customization. Private Cloud users may configure a similar domain DenyList.