Sessions changedgovernment/account/sessions
Nearest release: v2.1.319, published 15 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 6 Nov 2026 16:05 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 6 Nov 2026 16:07 UTC.
Upstream edited
Recorded here
Lines+19added
Lines−19removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits8to this page, all time
The whole hunk
from line 1, old and new numbered
/
from line 1
11# Sessions
22
3> Use this page to see every place you are currently signed in to Claude for Government and to sign out of any of them remotely.
3> See every place you are signed in to Claude for Government, sign any of them out, and check how long sessions last and what ends them.
44
55> **Who this is for:** Anyone with a Claude for Government account.
66
7Use this page to see every place you are currently signed in to Claude for Government and to sign out of any of them remotely.
7A session is created each time you sign in, whether that is in a web browser or in one of the Claude applications. The **Sessions** tab lists your active sessions and lets you sign out of any of them remotely.
88
9A session is created each time you sign in, whether that is in a web browser or in one of the Claude applications. This page lists your active sessions so you can confirm that nothing unexpected has access to your account, and clean up after yourself on a computer you no longer have.
10
119## What each row shows
1210
13Each row is one active sign-in. The one you are using right now is labeled **this session** and always appears at the top of the list; the rest are ordered with the most recent first.
11Each row is one active sign-in, and shows which kind of application it is for, how it was established, and when it started. The one you are using right now is labeled **this session**. These are some of the ways a session is established:
1412
15* **Client** tells you which kind of application the sign-in is for.
16* **via …** tells you how that session was established. **Single sign-on** means you authenticated through your agency's identity provider. **Device pairing** means a user entered a code shown in a Claude application and approved it in a browser, linking that application to your account. **Email link** means a one-time link was sent to your inbox and followed to sign in.
17* **Signed in** tells you when the session started. The time is shown in your local time zone along with a relative hint such as "2 days ago".
13* **Single sign-on** means you authenticated through your agency's identity provider.
14* **Device pairing** means a sign-in from a Claude application was approved in a browser, linking that application to your account.
15* **Email link** means a one-time link was sent to your inbox and followed to sign in. Only Primary Owners and tenant administrators can [sign in this way](https://claude.com/docs/government/tenant-admin/identity-and-access.md#emailed-sign-in-link).
1816
1917## What is not shown
2018
21To limit how much information about your devices is held in the system, the list deliberately does not include IP addresses, locations, device names, or browser details. You can tell a browser session from an application session and you can see when each one started, but you cannot tell two browser sessions apart by device. When in doubt, sign out anything you cannot positively account for; signing back in is quick.
19The list does not include IP addresses, locations, device names, or browser details. You can tell a browser session from an application session and you can see when each one started, but you cannot tell two browser sessions apart by device.
2220
2321## How long sessions last
2422
25Sessions expire after a period of inactivity, and using a session extends it. Once you have been inactive for longer than the idle timeout, that browser tab or application prompts you to sign in again the next time it tries to do anything. Your agency or organization sets the idle timeout, which is 24 hours unless they have changed it.
23Sessions expire after a period of inactivity, and using a session extends it. Your agency or organization sets the idle timeout, which is 24 hours unless they have changed it. After about that long without use, that browser tab or application prompts you to sign in again the next time it tries to do anything.
2624
2725Your agency or organization can set a maximum session length in addition to the idle timeout. When a session reaches that length, it expires even if you have been using it the whole time, and the browser tab or application prompts you to sign in again. Sessions that expire either way drop off this list automatically.
2826
29Sessions can also end early in these ways: you sign one out from this page, you use the **Sign out** button in the page footer to end the session you are currently using, or an administrator deactivates your account or your organization, which immediately invalidates every session you have.
27Sessions can also end early, for example in these ways:
3028
31When you sign in, Claude for Government can end another of your sessions. You can have up to six active sessions in each Claude application, such as Claude Desktop. You can also have up to three browser sessions in total. If a new sign-in goes over one of these limits, Claude for Government ends your session of the same kind that expires soonest.
29* You sign one out from this page.
30* You use the **Sign out** button in the page footer, which ends the session you are currently using.
31* An administrator signs you out everywhere, which ends every session you have.
32* Your agency moves you to another organization, which ends the sessions you already have.
33* An administrator deactivates your account or your organization, which immediately invalidates every session you have.
3234
35You can have up to six active sessions in each Claude application, such as Claude Desktop. You can also have up to three browser sessions in total. If a new sign-in goes over one of these limits, Claude for Government ends your session of the same kind that expires soonest.
36
3337## Signing out of other sessions
3438
35> [!NOTE]
36>
37> These controls only appear when you have sessions besides the one you are using. If this is your only sign-in, the list shows just the current session and no sign-out buttons.
38
3939* To end one session, select **Sign out** on its row.
4040* To end everything except the one you are using, select **Sign out *N* other sessions** below the list.
4141
42Neither of these affects the session you are currently using, and there is no confirmation prompt; the session is revoked as soon as you select the button. To sign out of the session you are using right now, use the **Sign out** button in the page footer instead.
42Neither of these affects the session you are currently using, and there is no confirmation prompt; the session is revoked as soon as you select the button.
4343
4444### What actually happens when you sign out another session
4545
46The sign-out is recorded the moment you select the button. The other browser or application is not sent a live message, but the very next thing it tries to do (load a page, send a message, or refresh) will be refused and it will be returned to the sign-in screen. In practice this means the other session is cut off within seconds of any activity. A request that was already in flight at the instant you revoked may finish, but nothing new can start.
46The other browser or application is not sent a live message, but the very next thing it tries to do (load a page, send a message, or refresh) will be refused and it will be returned to the sign-in screen. A request that was already in flight at the instant you revoked may finish, but nothing new can start.
4747
48Signing out another session from this page does not touch your agency's single sign-on session, so if the person at that other computer tries to sign back in, the identity provider may still let them straight through without re-entering a password. If that is a concern (for example, you left a shared computer signed in), sign the session out here first, then contact your agency's identity team to end the single sign-on session, or change your directory password.
48Signing out another session from this page does not touch your agency's single sign-on session, so if the person at that other computer tries to sign back in, the identity provider may still let them straight through without re-entering a password. If that is a concern (for example, you left a shared computer signed in), sign the session out here first, then contact your agency's identity team to end the single sign-on session.
4949
5050## If you see a session you don't recognize
5151
No line in this hunk matches that.