Deploy with Enterprise Admin Console changedthird-party/claude-desktop/admin-console
Nearest release: v2.1.296, published 2 hours after 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 9 Oct 2026 14:43 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 9 Oct 2026 15:07 UTC.
Upstream edited
Recorded here
Lines+5added
Lines−3removed
From line
85
where the diff opens
First seen
8 Sep 2026
this site's first read of the page
Recorded edits30to this page, all time
The whole hunk
from line 85, old and new numbered
/
from line 85
8585
8686Conversations from the earlier configuration stay on the device, and Claude Desktop copies them into the app's history automatically. On each device the copy runs once, in the background, the next time the app starts with the user signed in. The earlier Cowork, Chat, and Code sessions then appear in the app's sidebar. The originals stay in place, so the copied sessions use disk space a second time.
8787
88* **To turn the automatic copy off**, go to the **Connectors** page and, under **Claude.ai data import**, turn off the **Automatically import earlier third-party sessions** switch before users sign in. This sets `automatic3pImport` under [`claudeAiImport`](/docs/third-party/claude-desktop/configuration#claudeaiimport) to `false`. A device that already made the copy keeps it, and the app lists it under **Settings → Import & export → Import history**, where each user can remove the copied sessions.
88The copy also brings over each user's Cowork projects, artifacts, memory, and global instructions, and their scheduled tasks from Cowork and Code. It brings over the plugins they uploaded unless [`userPluginUploadsEnabled`](/docs/third-party/claude-desktop/configuration#userpluginuploadsenabled) is `false`, and the skills they saved unless [`skillCreationEnabled`](/docs/third-party/claude-desktop/configuration#skillcreationenabled) is `false`. Memory and global instructions apply right away, scheduled tasks and uploaded plugins stay on or off as they were, and new tasks use a project's instructions only after the user accepts them. See [Automatic import of earlier third-party sessions](/docs/third-party/claude-desktop/import#automatic-import-of-earlier-third-party-sessions) for each item.
89
90* **To turn the automatic copy off**, go to the **Connectors** page and, under **Claude.ai data import**, turn off the **Automatically import earlier third-party sessions** switch before users sign in. This sets `automatic3pImport` under [`claudeAiImport`](/docs/third-party/claude-desktop/configuration#claudeaiimport) to `false`. A device that already made the copy keeps it, and the app lists it under **Settings → Import & export → Import history**, where each user can remove the copied sessions and the projects copied with them.
8991* **If you import a configuration file exported from Claude Desktop**, check the **Automatically import earlier third-party sessions** switch after the upload. The exported file can mark this switch as off even if nobody turned it off, and the console keeps the value from the file.
9092* **To let users also import their claude.ai conversations**, or bring over anything the automatic copy left out, turn on the **Enable import** switch under **Claude.ai data import** on the **Connectors** page. This sets `enabled` under [`claudeAiImport`](/docs/third-party/claude-desktop/configuration#claudeaiimport) to `true`. Users then open **Settings → Import & export** in the app and click **Import…** to open the [import wizard](/docs/third-party/claude-desktop/import#open-the-import-wizard).
9193
from line 115
113115 Choose an interactive sign-in wherever your provider offers one. It is the recommended credential kind for a deployment managed from the console. Users sign in inside the app with their own accounts, and there is no shared credential to distribute to devices or rotate.
114116</Tip>
115117
116The console never holds a provider credential. The **Credential kind** field on the **Connection** page tells Claude Desktop how each user's device obtains one, and offers the kinds your provider supports: **Interactive sign-in** in the app, **Workforce Identity** (Google Cloud's Agent Platform only), **Cloud vendor profile** (an AWS profile or Google Cloud credentials file already on the device), or **Helper script** (a [credential helper](/docs/third-party/claude-desktop/credential-helper) on the device). Static API keys and bearer tokens aren't offered, because the console refuses to store them. The same **Connection** settings go to every user, so a credential kind that depends on something present on each device works only if your device management puts it there.
118The console never holds a provider credential. The **Credential kind** field on the **Connection** page tells Claude Desktop how each user's device obtains one, and offers the kinds your provider supports: **Interactive sign-in** in the app, **Identity provider sign-in (OIDC)** (for example, for [Amazon Bedrock behind an authenticating proxy](/docs/third-party/claude-desktop/bedrock#sign-in-with-your-identity-provider)), **Workforce Identity** (Google Cloud's Agent Platform only), **Cloud vendor profile** (an AWS profile or Google Cloud credentials file already on the device), or **Helper script** (a [credential helper](/docs/third-party/claude-desktop/credential-helper) on the device). Static API keys and bearer tokens aren't offered, because the console refuses to store them. The same **Connection** settings go to every user, so a credential kind that depends on something present on each device works only if your device management puts it there.
117119
118120| Provider | Recommended credential kind | Credential fields on the **Connection** page | What users do at first launch |
119121| - | - | - | - |
from line 247
245247
246248A user's Claude account can belong to your deployment's organization and to other Claude organizations, and the user can move between them in Claude Desktop. When such a user signs in, the app opens in their other organization and asks whether to switch to yours, with **Switch and restart** and **Not now** buttons. A user who chooses **Not now** isn't asked again on that device and can switch later by choosing your organization from the account menu. Each move into or out of your organization restarts the app, because third-party mode runs as a separate app configuration. To go back, the user chooses **Sign out** and signs in to Claude again after the restart. From Claude Desktop 1.49585.0, they can instead pick their other organization from the account menu, which also restarts the app and asks them to sign in.
247249
248To remove the choice, turn on **Require this organization in Claude Desktop** under **Desktop sign-in** on the **Connection** page. Members who also belong to another organization are then switched to yours the next time Claude Desktop starts or they sign in. Browsers are not affected.
250To remove the choice, turn on **Require this organization in Claude Desktop** under **Desktop sign-in** on the **Connection** page. Members who also belong to another organization are then switched to yours the next time Claude Desktop starts or they sign in. While they are in your organization, the account menu lists another of their organizations only if that organization has the same setting on. Browsers are not affected.
249251
250252### Configuration updates
251253
No line in this hunk matches that.