Inconsistent branding makes it look like phishing
A security alert that looks different from other product emails is the first thing users distrust.
SaaS email template
Fire security.new_login with device info and a secure-account link. else.events sends a consistent, branded security alert that users recognise and trust.
A security alert that looks different from other product emails is the first thing users distrust.
"A new login was detected" with no context is useless. Users need device type, approximate location and time to judge whether it was them.
"Was this not you?" with no link to immediately secure the account is a liability. Users need a one-click path to revoke access.
Security alert email logic buried in the auth service means every copy update requires a deployment.
Include device type, approximate location and login time in the event payload. The template renders "Login from Chrome on Mac, Frankfurt, Germany at 14:03."
Generate a secure-account or revoke-access URL in your backend. Include it in the payload. The template renders "Was this not you? Secure your account now."
Security alerts use the same MJML template base and brand variables. No phishing-like visual inconsistency.
Update security alert copy, add a locale or change the CTA text without touching the auth service.
{{ user.name }}Recipient name{{ user.email }}Account email address{{ data.event_type }}Security event type — new_login, password_changed, api_key_created{{ data.device }}Device type and browser (e.g. Chrome on Mac){{ data.location }}Approximate location (e.g. Frankfurt, Germany){{ data.timestamp }}Time of the security event{{ data.secure_account_url }}Link to revoke access or secure the accountDevice info, location, timestamp and a secure-account link — all from the event payload.