We are currently implementing Auth0 for authentication and authorization in our .NET + React-based multi-tenant SaaS application. We are using passwordless authentication with email magic links and would like to better understand the customization capabilities around this flow. We aim to enhance the passwordless magic link email with:
-
User-specific data (e.g., name, metadata)
-
Tenant-specific branding (e.g., logo, tenant name)
-
Custom-designed email templates aligned with our SaaS platform
We have a few specific questions:
-
Customization of Passwordless Magic Link Email
Could you please clarify the extent to which the default passwordless (magic link) email template can be customized?-
Are we limited to predefined variables such as
{{ link }}and{{ code }}? -
Is there any way to include additional dynamic data (e.g., user metadata, tenant-specific details)?
-
It would be helpful if you could share any official documentation outlining supported template variables and customization options.
-
-
Custom Email Sending via Backend
We are exploring whether it is possible to send the passwordless magic link email from our own backend (e.g., using SendGrid or another provider) to achieve full control over branding and content.-
Is there a supported approach for this using Auth0 APIs?
-
Can the magic link be generated or retrieved programmatically (e.g., via
/passwordless/startor any other endpoint)? -
If not directly supported, are there recommended patterns or best practices for implementing a custom-branded passwordless experience while still leveraging Auth0?
-
-
Template Variables / Liquid Support
-
Does Auth0 support Liquid templating or any equivalent templating engine for passwordless emails?
-
What variables are officially supported in passwordless email templates?
-
Are there any extensibility points (Actions, Hooks, etc.) that can inject additional data into the email template?
-