
Send a password changed email after your system confirms the update. Tell the recipient what changed and when. If they recognize the change, no action is needed. If they do not, point them to a recovery or support route they can reach independently of the email.
Password changed email template
This example uses Northstar, a fictional service. Replace the bracketed fields with the confirmed change time and the support route your team actually provides.
Subject · Your Northstar password was changed
Preview text · If you don’t recognize this update, contact us through the Northstar Help Center.Hi,
The password for your Northstar account was changed on [date] at [time and time zone].
If you made this change, you don’t need to do anything.
If you don’t recognize it, open Northstar the way you normally do and go to Help Center → Account security. If you can’t sign in, use [public account recovery route available without sign-in].
The Northstar team
Make the route usable for someone who has lost access. If the Help Center sits behind sign-in, give the public route directly and check it in a signed-out browser. Never include a password, a recovery code or a reset token in the notification. OWASP recommends notifying users when a reset is complete and leaving the password out of the message. OWASP Forgot Password Cheat Sheet
Tie the notification to the completed change
| What happened | What to send |
|---|---|
| The user requested a reset and the password remains unchanged | Use the reset-request flow if the account is eligible. |
| The password was successfully updated in account settings | Send the password changed notification. |
| The user completed password recovery and saved a new password | Send the same notification after the update succeeds. |
| The request failed, expired or was abandoned | Keep the completed-change notification unsent. |
A reset-request email asks the user to take an action. This alert tells them about a change that already happened. For the earlier step, use the password reset email template and checklist.
Test the notification and support route
- Test both successful paths. Change the password in account settings and complete a recovery in a test account. Check that the alert arrives at the intended address and shows the right time zone.
- Test a failed change. Leave a reset unfinished. Check your send records to verify that the completed-change alert stayed unsent.
- Check duplicate events. Process the same confirmed change event twice in your test environment. Verify that the recipient receives one alert for that event.
- Check the alert while signed out. Follow the words in the message from a fresh browser session. Confirm that someone who can't sign in can reach the recovery or support form and tell your team they don't recognize the update.