Review account security activity
Check the last 90 days of personal sign-in, password, and MFA activity.
Recent Account Protection History shows security events for your own team-app login. It is a 90-day personal history, not a workspace-wide or permanent audit log.
Open your security history
- Open Personal Settings → Security.
- Find Recent Account Protection History.
- Scroll through the list. Older rows load as you reach the end.
If no matching events exist, Sydnee shows No recent security activity in the last 90 days. If the list cannot load, refresh the page before you use it to judge account safety.
Events you may see
The history can include:
- Signed in, signed out, or a new workspace session started.
- Password changed.
- Password reset requested or completed.
- MFA turned on or off.
- MFA check issued, completed, or invalidated.
- MFA backup code used or made again.
- A support-led MFA recovery action.
An event can show its time, device type, country, and IP address when those details are available. A country is an estimate based on the network address. It may be missing or different when a person uses a mobile network, company network, or VPN.
Review active sessions
The same Security page has Active Sessions. It lists the current login and other active team-app sessions.
If you see another session you no longer use, select Log Out for that session. Sydnee asks for an authenticator code, backup code, or emailed verification code before ending it. This control ends other sessions only.
What should I do if I do not recognize an event?
- Check the exact time, device, country, and IP address.
- End any other active session you do not recognize.
- Change your password.
- Turn on MFA. If MFA is already on, regenerate the backup codes.
- Contact support if the event still looks wrong.
Send the visible event type and time. Do not send your password, MFA code, backup codes, QR code, or authenticator secret.
Why is an expected event missing?
- The history covers only your own login, not another team member.
- The event may be more than 90 days old.
- Some normal product actions are not security events.
- The newest page may need a refresh after a change.
- A failed load is not the same as an empty history.