Sessions and devices
Where to see signed-in devices, how to revoke one session or all others, whether signing out affects other devices, and why sessions expire.
Which devices am I signed in on
Sessions in account settings lists the active sessions, each with the device, last-active time and approximate location. It shows only this account's sessions; nothing crosses accounts.
How to kick a device off
Two granularities:
| Action | Effect |
|---|---|
| Revoke one session | Only that device stops working; others are untouched |
| Revoke all other sessions | Keep the current device, kill everything else |
Revocation takes effect immediately: that device's session credential dies and its next request is rejected.
Does signing out on one device affect others
By default, no. Signing out ends only the current device's session. To end everything, use "revoke all other sessions".
Why sessions expire
Sessions have a lifetime, and signing in again is required afterwards. That is by design: a session that never expires keeps an attack window open forever once leaked.
Sessions can also end early when:
- you revoke it elsewhere;
- the password is reset (this usually ends existing sessions);
- security policy ends it after detecting an anomalous sign-in.
An unfamiliar device shows up
Revoke it first, then follow the order in Account and security: revoke sessions → remove suspicious verification methods → check authorized applications → reset the password.
Related
- Full list of reasons you may be asked to sign in again: Sign-in and verification
Verification methods
What passwords, passkeys, authenticators, recovery codes and email each do, why keeping two methods matters, and how recovery codes are consumed.
Sign-in and verification
Questions about the sign-in step itself — why you are asked to sign in again, why you are asked to verify once more, and what to do when verification fails.