Skip to main content
Archie Auth sends the emails your users need to sign up, sign in, and stay safe. You word each one, add your logo, colour, and sender name, and set the wording per language. Everything is customizable per environment, in the dashboard or via the GraphQL API. Links, codes, and passwords are always added by Archie. You never type them into an email.

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 with configureProjectAuth. 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.
See the full GraphQL API reference for every field on the configureProjectAuth input.

Branding via GraphQL

Set the branding programmatically with the same configureProjectAuth 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 senderName field overrides the SendGrid “From Name” without changing the verified sender email address (which stays platform-managed).
  • Branding is per-environment — staging and master can 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

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.
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.
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.
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.
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.