Email & SMS templates

Every message Atlas sends — verification codes, magic links, password resets, invitations — is a template you can edit. Each instance ships with a built-in default for every template; when you customize one, Atlas stores an override and leaves the default in place so you can always revert.

The templates

Atlas has templates for the transactional messages it sends, including:

• Email verification (code and magic link)

• Password reset

• Organization invitation

• SMS verification code

Each is listed under Customization → Emails and Customization → SMS with its current override (if any) shown next to the built-in default.

Variables

Templates use {{variable}} placeholders that Atlas fills in at send time. The dashboard shows the variable schema each template supports — for example an OTP template exposes {{code}}, and messages include your app name and links. When you save an override, Atlas validates it with the same code the mailer uses, so a template that references an unknown variable — or an SMS template that drops the required {{code}} — is rejected at save time rather than failing silently when a user is waiting for a login code.

Edit a template

1. Open Customization → Emails (or SMS).

2. Pick a template. You'll see the built-in default and the variable schema.

3. Edit the subject/body, keeping the required variables.

4. Save. Atlas validates it and stores the override for this instance.

5. To revert, Reset to default drops the override and the built-in template renders again.

Sending: bring your own provider

Atlas doesn't send from a shared address — outbound email and SMS are per-instance and delivered through a provider you configure (BYOK). Configure a provider under Messaging for the instance so verification and reset messages actually deliver. For deliverability, verify your sending domain (SPF, DKIM and a DMARC policy) at the provider or auth mail lands in spam.

Next

Serve sign-in from your own domain → Custom domains.