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.
SaaS email template
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.
"A new login was detected" with no device or location is noise, not signal. Users ignore it after the second time.
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.
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.
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.
Your auth service fires security.login_from_new_device for every login from an unrecognised device fingerprint. No inconsistency.
Device name, browser, location, login time — included in the event payload. The template renders a complete, useful alert.
Include a revoke_access_url in the payload. The template renders a one-click "This was not me — revoke access" button.
Consistent branding, same sender name, same logo. Users recognise the email as legitimate.
{{ 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 accountDevice, location, time and one-click revoke. Consistent branding that does not look like phishing.