Agent WranglersSessions and security activity Recommended
Show people their own security log
Keep a log of each person's security events and show it to them in settings for at least 90 days.
How to do it
Record sign-ins, failed sign-ins, factor and email changes, recoveries, ended sessions, data exports and every staff visit to the account. Store the event, the time, the device label and the approximate place. Never store passwords, tokens or full IP addresses there, as keep only what you need asks. Write the log append-only, apart from the session and user tables. Give organisation owners the same view of their members, with a CSV or JSON export. The security logging rule covers what operations alert on.
Example
{"time":"2026-11-02T09:15:04Z","user":"u_7c1e","event":"factor.added","factor":"passkey","name":"Work laptop","device":"Firefox on Windows","place":"Gothenburg, SE"}How to check
On a test account, sign in, add a passkey and export data. Settings shows three new events with their times. The log holds no token and no IP address.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers accounts playbook: https://agentwranglers.se/playbook/accounts/sessions-and-security-activity/security-activity-log.