Session History
Session History is the record of every sign-in and failed attempt for the business unit in the header, kept for one year.
Video coming soon: Session History in 2 minutesThis is a list screen, so it has "What you see" and "What you can do".
Where to find it
Configuration › Security › Session HistoryWhat you see
| Column | What it shows |
|---|---|
| User | The email used. A failed attempt on an address with no account says "No matching account". |
| Outcome | Success, or Failed with the reason, for example Wrong password, Wrong OTP, Wrong PIN, Wrong MFA code, Account locked or Account deactivated. |
| Method | How they signed in: Password, Email OTP, PIN, PIN unlock, Authenticator app, MFA backup code, Google, Microsoft, Sign-up, Invite accepted, or a shared-link OTP or PIN. |
| Source | App, Admin or Undeclared. |
| Signed in and Signed out | Times, and how it ended: Signed out, Revoked by admin, Password reset, Replaced by a newer sign-in, Expired, or Still active (with its expiry). |
| Device / Browser, IP | Where it came from. |
What you can do
- Filter by user, outcome (All attempts, Successful only, Failed only), sign-in source and a From and To date. Click Clear filters to reset.
- Page through results, and change the rows per page (25 by default).
A non-admin sees only their own rows.
What changes for your team
Nothing; the screen only reads. Use it to see who signed in, to spot repeated failures and to check whether a revoked session ended.
What is not on this screen
No export or import, no edit and no free-text search. Entries older than a year are gone. Platform staff additionally get a business-unit filter.
On mobile
Not on the phone. Use the admin portal in a web browser; sign-ins from the phone are recorded here as App. The Android app is on Google Play. The iPhone app is coming soon to the App Store. Same on iPhone and Android.
Problems and fixes
"Failed to fetch session history"
Reload and try again.
"No sign-in activity found for this filter"
Widen the dates or clear the filters.