The account emails
Edit an email
Open App Services → Authentication Providers → Archie Auth → Emails. The Account e-mails editor lists every email on the left. Select one, then pick the language to edit. Each language starts with Archie’s default wording. To change it, click Write my own. The editor starts from the text your users already receive. To go back, use Use Archie’s default for this language. Resetting one language or one email doesn’t touch the others. For each language you set:Body blocks
Each email offers only the blocks that make sense for it. An email that carries a link, a code, or a password must keep that block. If your text is missing it, or can’t be used for a language, Archie sends its default wording for that language instead. The editor flags the email with a problem marker and lists what to fix, and nothing is saved until you fix it.
Variables
Use variables in subject, preheader, paragraphs, and footer. Write them as{{firstName}}, or use the variable buttons in the editor.
Two-factor notices also offer
{{occurredAt}} and counters of the factors and recovery codes removed or kept. Codes, links, passwords, and tokens (otp, temporaryPassword, inviteUrl, actionUrl, magicLinkUrl, token) are never variables. Archie adds them through blocks.
Languages
Archie sends emails in English or Spanish. Set Default language for e-mails in the Sender section. The default language is marked (default) in the language tabs. Edit each language separately.Sender
Branding
Branding applies to every email and language. The layout stays consistent. Only the branding slots change. Sender and branding changes show in the preview once saved.
Preview and test
The Preview panel renders the email as your users will see it, with sample data, and updates as you edit. It shows the saved email, or Archie’s default when none is saved. Use Preview variant for emails that have more than one version, such as the activation link and the notice. A notice carries no link or secret and always uses Archie’s wording. Click Send test to me to send the email to your own address with sample data. Test emails go only to your own verified address. Only a project owner, project admin, or organization admin can send them.Templates are per-environment. Editing the template in
staging doesn’t affect master. Branching an environment doesn’t copy templates. Start from the default in the new environment, or copy the wording manually. Only a project owner, project admin, or organization admin can change account emails.Customizing via the GraphQL API
For codified configuration, set the verification and recovery templates withconfigureProjectAuth. The other emails are edited in the dashboard.
The editor above and this GraphQL input are not the same shape. In the GraphQL input, the code appears as
{{otp}} inside the body.configureProjectAuth input.
Branding via GraphQL
Set the branding programmatically with the sameconfigureProjectAuth mutation. senderName is the Sender name (From) field.
Branding behavior
- Custom branding overrides Archie’s defaults in the header, footer, and sender name.
- The overall email layout — structure, responsiveness — stays consistent. Only the branding slots change.
- Empty fields fall back to platform defaults.
- The
senderNamefield overrides the SendGrid “From Name” without changing the verified sender email address (which stays platform-managed). - Branding is per-environment —
stagingandmastercan use different logos and company names.
Email delivery
Two transports back the same MJML templates:
The transport is configured at the platform level and isn’t changeable per project. Both transports deliver identical emails.
For projects routing through SendGrid, see the SendGrid integration.
Rate limiting
Email sending is rate-limited to 5 emails per user per hour to defend against abuse (someone repeatedly triggering recovery emails to flood an inbox).FAQ
Why aren't templates copied when I branch an environment?
Why aren't templates copied when I branch an environment?
Same reason auth secrets aren’t — environment isolation. Branching a
staging environment from master shouldn’t silently propagate template wording you might be testing. Copy manually if you want them to match.Can I add my own variables to a template?
Can I add my own variables to a template?
Only the variables listed in Variables are supported. Anything else in
{{...}} is rendered as literal text. To inject more context, do it server-side via the auth events and send your own email through a custom function.The user reports they didn't receive the email — what do I check?
The user reports they didn't receive the email — what do I check?
First, the spam folder. Then verify the address in the user record (typos at signup are common). If consistently undelivered, check transport-level delivery logs in your email provider (SES or SendGrid) and confirm the sender domain’s DKIM / SPF records are valid.
Can I send a custom email from auth events?
Can I send a custom email from auth events?
Yes — subscribe to events like
auth.user.registered from a custom function or webhook and send your own email via the integrated provider. The built-in templates handle account emails such as codes, links, and notices; everything else (welcome flow, marketing onboarding) is yours.Does the senderName appear in the From: header?
Does the senderName appear in the From: header?
Yes — it overrides the display name. The sender email address stays the platform-verified address, which is what the receiving mail server validates against DKIM / SPF.