SaaS email template

Team invitation email — clear, role-aware and with a working accept link

Fire team.invited with the invitee email, role and accept URL. else.events sends a branded invitation that converts to accepted teammates.

Common mistakes with team invitation emails

No expiry shown on the invite link

Team invite links often expire after 48–72 hours. Not telling the invitee this leads to broken link confusion and support tickets.

Role not shown in the email

The invitee wants to know what role they are being given before they accept. "You have been invited" with no role context is less informative.

No mention of who sent the invite

"You have been invited to join Acme" without naming the inviter feels impersonal and slightly suspicious.

Generic accept link that requires login first

An invite link that drops the user on the login page instead of the accept-invite page creates friction and reduces acceptance rates.

Inviter name, role and expiry in the payload — trust in the email

Include inviter name and role in the event payload

"Alex from Acme has invited you to join as Editor" — personalised from the event payload. No vague invitations.

Direct accept URL from the payload

Include the full accept URL in the payload. The link takes the invitee directly to the accept-invite flow — no login wall first.

Expiry shown clearly

Include invite_expires_at in the payload. The template renders "This invite expires in 48 hours".

Managed outside your team service

Edit invitation copy, add a locale or change the CTA text without touching the team invitation code.

Template variables for the team invitation email

  • {{ user.email }}Invitee email address (the recipient)
  • {{ data.inviter_name }}Name of the person who sent the invite
  • {{ data.workspace_name }}Workspace or organisation name
  • {{ data.role }}Role the invitee is being given (Editor, Viewer, Admin)
  • {{ data.accept_url }}Unique, time-limited accept-invite link
  • {{ data.invite_expires_at }}Invite expiry time — shown in the email

Frequently asked questions

What subject lines work for team invitation emails?
"Alex has invited you to join Acme on [App]", "You have been invited to [Workspace] — accept your invite", "[App] team invite from Alex". Include the inviter name and workspace for trust.
How do I handle invites to users who do not have an account yet?
Your accept URL should handle both cases — existing users are logged in automatically on click; new users are taken to a signup+accept flow. This URL logic lives in your backend; else.events just renders whatever URL you include in the payload.
How long should team invites be valid?
Typically 48–72 hours. Show the expiry clearly in the email. Your backend controls the token lifetime and includes the expiry in the event payload.
Can I re-send an invitation?
Yes. Your app fires a new team.invited event with a fresh token and URL. else.events sends a new invitation email. The previous token should be invalidated in your backend.

Team invitation emails that get accepted

Inviter name, role and direct accept link — personalised from the event payload.

  • Inviter name and role from payload
  • Direct accept URL — no login wall
  • Expiry shown clearly in the email