Customizing email templates
Customizing local email templates using config.toml.
You can customize the email templates for local development using the config.toml
settings.
Configuring templates
You should provide a relative URL to the content_path
parameter, pointing to an HTML file which contains the template. For example
Available email templates
There are several Auth email templates which can be configured:
auth.email.template.invite
auth.email.template.confirmation
auth.email.template.recovery
auth.email.template.magic_link
auth.email.template.email_change
Template variables
The templating system provides the following variables for use:
ConfirmationURL
Contains the confirmation URL. For example, a signup confirmation URL would look like:
Usage
Token
Contains a 6-digit One-Time-Password (OTP) that can be used instead of the ConfirmationURL
.
Usage
TokenHash
Contains a hashed version of the Token
. This is useful for constructing your own email link in the email template.
Usage
SiteURL
Contains your application's Site URL. This can be configured in your project's authentication settings.
Usage
Contains the user's email address.
Usage
NewEmail
Contains the new user's email address. This is only available in the email_change
email template.
Usage
Deploying email templates
These settings are for local development. To apply the changes locally, stop and restart the Supabase containers:
For hosted projects managed by Supabase, copy the templates into the Email Templates section of the Dashboard.