Sessions & Devices
The Devices page lets you see every active sign-in session on your SingleSign account. Reviewing your sessions regularly helps you spot unauthorized access and keep your account secure.
What are sessions?
A session represents an active sign-in to your SingleSign account. Every time you sign in from a device or browser, a new session is created. Sessions remain active until you sign out or they expire.
Why review sessions?
Regularly checking your active sessions helps you:
- Detect unauthorized access — if you see a session from a device or location you don't recognize, someone else may have access to your account.
- Clean up old sessions — sign out of devices you no longer use.
- Verify your own activity — confirm that recent sessions match your actual usage.
How to view your sessions
- Sign in to your SingleSign account at singlesign.com.
- Go to Account → Devices.
- You'll see a list of all active sessions.
What each session shows
Each session entry includes:
- Device type — desktop, mobile, or tablet.
- Browser — the web browser used (e.g., Chrome, Firefox, Safari).
- Location — approximate geographic location based on IP address.
- Last active — the most recent time the session was used.
How to revoke a session
If you see a session you don't recognize or no longer need:
- Find the session in the list.
- Click "Sign out" next to the session.
- The session is immediately terminated.
- The device will need to sign in again to access your account.
What to do if you see an unfamiliar session
If you notice a session you didn't create:
- Revoke it immediately by clicking "Sign out."
- Change your password right away.
- Review your connected apps to make sure nothing was authorized without your knowledge. Manage connected apps →
- Enable MFA if you haven't already. Set up MFA →
Last updated: 2026-02-16
Related articles
- Help CenterFind answers about using SingleSign to sign in, manage your privacy, and secure your account.
- free identity providerSingleSign pricing in one line: sign-in is free, with no monthly-active-user meter. See exactly what is included, and what SingleSign Mail costs for businesses.
- Identity provider alternativesIdentity provider alternatives, by the provider you are leaving: what actually has to change in your code, and what does not.
- Auth0 comparisonSingleSign vs Auth0 compared on the difference that matters: who owns the account. A side-by-side table, then the three cases where each one is the right call.
- Okta comparisonSingleSign vs Okta: Okta is built for workforce identity inside a company, SingleSign for consumer sign-in across applications.
- Firebase Auth comparisonSingleSign vs Firebase Authentication on lock-in, portability and consent, plus the cases where staying on Firebase is right.
- SingleSign vs Google Sign-InSingleSign vs Google Sign-In: the same one-tap convenience, without an advertising business behind the identity.
- alternative to Auth0Auth0 alternatives compared, plus the part most listicles skip: what migrating off Auth0 actually involves, which code changes, and which does not.
- alternative to OktaOkta alternatives for teams that need customer sign-in rather than workforce identity. The table first, then what changes when you move consumer auth off Okta.
- Firebase Authentication alternativesFirebase Authentication alternatives for teams leaving Google Cloud or wanting a standalone OIDC provider. Comparison table, then the real migration path.
- SaaS single sign-onSSO for SaaS applications using OAuth 2.0 and OpenID Connect: the flow to pick, the scopes to request, and a working integration path with SingleSign.
- Authentication for startupsAuthentication for startups without a monthly-active-user meter: standards-based OAuth 2.0 sign-in you will not have to replace when the product finds traction.