SaaS email template

New login from new device email — build trust at every login

Fire security.login_from_new_device with device and location data. else.events sends an immediate, branded alert that reassures legitimate users and warns compromised ones.

Why new login alerts fail to build trust

Too vague to be useful

"A new login was detected" with no device or location is noise, not signal. Users ignore it after the second time.

No action if it was not the user

An alert with no revoke-access link forces a compromised user to navigate to settings while panicking. The link should be one click away in the email.

Looks different from the rest of the product

New-login alerts built separately from the main email system often have inconsistent styling — which makes them look exactly like the phishing emails they are trying to prevent.

Only sent on some devices or some login methods

Inconsistent new-login alerts undermine the trust they are supposed to build. If users sometimes get them and sometimes do not, they stop trusting them.

Device, location, time, revoke link — all from the event payload

Fire from every new-device login consistently

Your auth service fires security.login_from_new_device for every login from an unrecognised device fingerprint. No inconsistency.

Full context in the payload

Device name, browser, location, login time — included in the event payload. The template renders a complete, useful alert.

Revoke-access link in the email

Include a revoke_access_url in the payload. The template renders a one-click "This was not me — revoke access" button.

Same template base as all product emails

Consistent branding, same sender name, same logo. Users recognise the email as legitimate.

Template variables for the new login email

  • {{ user.name }}Recipient name
  • {{ data.device }}Device and browser (e.g. Safari on iPhone)
  • {{ data.location }}Approximate location of the login
  • {{ data.login_at }}Date and time of the login
  • {{ data.revoke_access_url }}One-click link to revoke the session or lock the account

Frequently asked questions

What subject lines work for new login alerts?
"New login to your [App] account — was this you?", "Login from Safari on iPhone detected", "New device login — [App] security alert". Include device info in the subject for immediate context.
How do I determine if a device is "new"?
Your backend tracks device fingerprints per user (browser, OS, IP hash). If the login comes from a fingerprint not seen before, fire the event. else.events does not make this determination — it just sends the email when it receives the event.
Should I send this for every login or only new devices?
Only new devices. Sending a login alert for every login trains users to ignore them. The alert is only useful when the device is genuinely new or unrecognised.
What should the revoke-access link do?
It should immediately invalidate the session associated with the new login and optionally lock the account. The URL should be pre-authenticated or use a short-lived token — the user should not need to log in to revoke access.

New login alerts that users trust — and that protect them

Device, location, time and one-click revoke. Consistent branding that does not look like phishing.

  • Full login context from the event payload
  • One-click revoke-access link
  • Consistent branding with all product emails