Anythink maintains a set of system email templates, one for each triggered event. You can edit the subject line and body content of any template to match your product's tone and branding.
| Template | When it is sent |
|---|---|
| Email Confirmation | When a new user registers — they must confirm before their account activates |
| User Invitation | When you invite a user to your project via the dashboard or CLI |
| Password Recovery | When a user requests a password reset |
| Email Change | When a user updates their email address |
| Added to Organisation | When a user is added to your organisation |
Changes take effect immediately — the next time that event is triggered, the updated template is used.
Each template has access to a set of variables that are automatically substituted at send time. Use double curly braces to insert them:
{{ OrgName }}
{{ Email }}
{{ ConfirmationUrl }}
{{ PasswordResetUrl }}
{{ InviteUrl }}
{{ DashboardUrl }}
Commonly used variables:
| Variable | Description |
|---|---|
{{ OrgName }} |
Your organisation or project name |
{{ Email }} |
The recipient's email address |
{{ ConfirmationUrl }} |
Link the user clicks to confirm their email |
{{ PasswordResetUrl }} |
Link the user clicks to reset their password |
{{ InviteUrl }} |
Link the user clicks to accept an invitation |
{{ DashboardUrl }} |
Direct link to the dashboard |
{{ Token }} |
The one-time token (if you need to build a custom URL) |
The available variables differ slightly between templates — use the Preview panel to see exactly which variables are in scope for each template.
To make emails feel like they come from your product rather than Anythink:
{{ OrgName }} in all templatesEmails are sent from Anythink's shared sending infrastructure. If you need emails to come from your own domain (e.g. noreply@yourapp.com), this is available on higher-tier plans — contact support to configure custom sending.