Skip to main content

Templates and managed emails

Templates control the content users receive. Built-in emails cover common account, security, verification, recovery, and lifecycle messages.

Switera email template library with empty-state actions
Use Templates for invitation and custom product messages.
Switera built-in transactional emails catalog
Use Built-in to review account and security emails that Switera can manage for the app.

Invitation template checklist​

A good invitation email includes:

  • recognizable app or company name
  • clear reason the recipient is receiving the email
  • organization or workspace name when relevant
  • direct call to action
  • expiration or next-step expectation
  • support path or reply-to mailbox if users may be confused

Create a template​

  1. Open Services > Email.
  2. Open Templates.
  3. Select Create template or Start from example.
  4. Write the subject.
  5. Write short body copy.
  6. Insert only the variables your template needs.
  7. Preview the message.
  8. Save.
  9. Send a test before broad use.

Variables​

Templates can use variables for app, organization, inviter, recipient, and action links. Keep fallback copy readable so the email still makes sense when optional values are missing.

Avoid exposing raw internal IDs in user-facing emails unless your support process explicitly needs them.

Built-in emails​

Review built-in emails before launch:

  • email verification
  • magic link sign-in
  • passwordless code
  • password reset
  • welcome email
  • invitation accepted
  • MFA enabled or disabled
  • password changed

For each email, decide whether it is in use, available later, or not needed for this app.

Automation and timing​

Use Automation to understand when each message sends.

Switera email automation workflows and timing controls
Automation shows the trigger, timing, and active state for each account or lifecycle workflow.

Review:

  • trigger event
  • delay or immediate send behavior
  • whether a workflow is active
  • blocked recipient handling
  • whether the workflow uses a custom or built-in template

Test checklist​

  • invitation renders correctly
  • verification email reaches the inbox
  • recovery email works
  • links go to the expected hosted flow
  • reply-to goes to a monitored mailbox
  • unsubscribed or suppressed recipients are handled correctly
  • audit logs show major email configuration changes

Related pages: