Home Docs Claude Documentation

One capture · claude-docs

One read of Claude Documentationclaude-docs-20261014T190710Z

1 pages moved out of 265 read.

Pages moved 1 significant first

Pages read 265 in this capture

Captured 14 Oct 2026 19:07 UTC

Corpus hash 709219e553cb corpus-hash

What this read moved

1-1 of 1

third-party/claude-desktop/admin-console Changed · +68 / -16 lines

## Migrate an existing fleet to the admin console ### What is migrated ### What is not migrated

from line 76

7676

7777The console fills in the matching settings and lists anything in the file that it can't store, such as credentials, bootstrap keys, and values that are set automatically from your organization, like the display name. It then shows every change against the saved configuration, and replaces the configuration when you click **Replace configuration**. If the connection in the file can't be stored, for example because it relies on an API key or token in the file, the console keeps your saved connection instead.

7878

79Before the users of an existing fleet sign in, prepare their devices:

79If the file was exported from Claude Desktop, check the **Automatically import earlier third-party sessions** switch on the **Connectors** page 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.

8080

81* **MDM or bootstrap fleets:** remove the Claude Desktop configuration profile or registry policy, including a profile or policy that carries only bootstrap keys. A profile that sets only the [app-behavior keys](/docs/third-party/claude-desktop/mdm#update-keys-and-managed-precedence) can stay. For a device that keeps a profile with any other key, see [Devices with a managed profile](#devices-with-a-managed-profile).

82* **Machines configured in the app:** a device set up from the [in-app configuration window](/docs/third-party/claude-desktop/in-app-configuration) with **Apply Changes** stays in its local third-party configuration. Return it to standard Claude Desktop first. To do that, sign out in the app and choose the Anthropic sign-in option on the sign-in screen, as described under [Single-machine setup](/docs/third-party/claude-desktop/installation#single-machine-setup).

81To move the devices and users of an existing fleet to this configuration, see [Migrate an existing fleet to the admin console](#migrate-an-existing-fleet-to-the-admin-console).

8382

84Users then sign in as described under [Onboard users](#onboard-users).

86Conversations 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.

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.

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.

91* **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.

92* **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).

9483### What you can configure

9584

9685From the console you can set the same [configuration keys](/docs/third-party/claude-desktop/configuration) that MDM and bootstrap delivery support, apart from the items listed under [Limitations](#limitations). The **Desktop 3P** section of the left navigation has these pages:

from line 300

311300

312301If a setting is changed that affects where users' apps connect or sign in, or what can run on their devices (including when permission policies are added, removed, or reordered), Owners receive an email alert with the identity of the administrator who made the change.

313302

303## Migrate an existing fleet to the admin console

304

305If your fleet gets its Claude Desktop configuration from [MDM](/docs/third-party/claude-desktop/mdm), a [bootstrap server](/docs/third-party/claude-desktop/bootstrap), or the [in-app configuration window](/docs/third-party/claude-desktop/in-app-configuration), you can move it to the admin console and keep your inference provider, unless that provider is the [Claude API](#limitations). Users' earlier work [stays on each device](#where-your-data-goes). The app copies that work on the same device so it appears under your organization. Try these steps on a test device first.

306

307<Steps>

308 <Step title="Import your configuration">

309 Upload your current configuration, as described under [Start from an existing configuration file](#start-from-an-existing-configuration-file). Put settings that differ between groups of users in [per-group permission policies](#per-group-permission-policies).

310 </Step>

311

312 <Step title="Finish the configuration before users sign in">

313 Set every setting you rely on in the console, because the console's configuration replaces the profile's. Add your [plugin marketplaces](#plugin-marketplaces) on the **Plugins** page. To migrate users' work, check that the **Automatically import earlier third-party sessions** switch under **Claude.ai data import** on the **Connectors** page is on (the default). To skip the migration, turn it off. Devices that already migrated keep their items.

314

315 <Warning>

316 The app migrates users' work once on each device, the next time it starts after the user signs in to your organization. It skips uploaded plugins, saved skills, and scheduled tasks if the console has turned that feature off, and optional plugins that your organization doesn't offer yet. Changing those settings later doesn't migrate the skipped items.

317 </Warning>

318 </Step>

319

320 <Step title="Update Claude Desktop">

321 Update devices to Claude Desktop 2.37337.1 or later. Earlier releases migrate fewer items.

322 </Step>

323

324 <Step title="Remove the managed profile">

325 Remove the Claude Desktop configuration profile or registry policy, including one that carries only bootstrap keys. You can keep a profile that sets only the [app-behavior keys](/docs/third-party/claude-desktop/mdm#update-keys-and-managed-precedence).

326

327 * **Devices that keep a profile with any other key**: see [Devices with a managed profile](#devices-with-a-managed-profile)

328 * **Devices configured in the app**: the user signs out and chooses the Anthropic sign-in option, as described under [Single-machine setup](/docs/third-party/claude-desktop/installation#single-machine-setup)

329 </Step>

330

331 <Step title="Have users sign in">

332 Have users sign in to Claude with their work email address and restart the app when asked, as described under [Onboard users](#onboard-users).

333 </Step>

334</Steps>

335

336### What is migrated

337

338The app migrates these items in the background. The originals stay in place, so migrated sessions use disk space a second time.

339

340* Chat, Cowork, and Code sessions

341* Cowork projects

342* Artifacts

343* Memory, unless the user paused it

344* Users' global instructions and **Instructions for Claude**, unless they already set them in your organization

345* Scheduled tasks from Cowork and Code, except one-time tasks

346* Plugins that users uploaded, unless [`userPluginUploadsEnabled`](/docs/third-party/claude-desktop/configuration#userpluginuploadsenabled) is `false`

347* Skills that users saved, unless [`skillCreationEnabled`](/docs/third-party/claude-desktop/configuration#skillcreationenabled) is `false`

348* Optional organization plugins that users turned on, if you offer them from your plugins directory or from a marketplace that your inference gateway serves

349

350[Automatic import of earlier third-party sessions](/docs/third-party/claude-desktop/import#automatic-import-of-earlier-third-party-sessions) describes the migration for users, including how to remove migrated sessions and projects.

351

352### What is not migrated

353

354Users set up these items again:

355

356* **Organization plugins from other marketplaces, such as a git repository**: install them again from **Customize → Plugins → Discover → Organization**

357* **Plugins from marketplaces the user added**: add the marketplace and install the plugins again

358* **One-time scheduled tasks**: create them again

359* **App preferences**: set the model, per-tool permissions, and notifications again

360* **Connected folders in Cowork sessions**: connect the folders again

361* **"Always allow" choices in Cowork sessions and scheduled tasks**: approve again when a session or task asks

362* **Connector sign-ins**: sign in again to any connector that asks

363

364To let users import their claude.ai conversations, and any local sessions that the migration left out, with the [import wizard](/docs/third-party/claude-desktop/import#open-the-import-wizard), turn on the **Enable import** switch (off by default) under **Claude.ai data import** on the **Connectors** page.

365

314366## Devices with a managed profile

315367

316A managed profile is a macOS configuration profile, a Windows registry policy, or the Linux `/etc/claude-desktop/managed-settings.json` file, from [MDM](/docs/third-party/claude-desktop/mdm) or [bootstrap](/docs/third-party/claude-desktop/bootstrap) delivery. A device whose profile sets any key other than the [app-behavior keys](/docs/third-party/claude-desktop/mdm#update-keys-and-managed-precedence) uses the profile's configuration until its user moves the device to the admin console's configuration. Where you can, remove such a profile before users sign in, as described under [Start from an existing configuration file](#start-from-an-existing-configuration-file).

368A managed profile is a macOS configuration profile, a Windows registry policy, or the Linux `/etc/claude-desktop/managed-settings.json` file, from [MDM](/docs/third-party/claude-desktop/mdm) or [bootstrap](/docs/third-party/claude-desktop/bootstrap) delivery. A device whose profile sets any key other than the [app-behavior keys](/docs/third-party/claude-desktop/mdm#update-keys-and-managed-precedence) uses the profile's configuration until its user moves the device to the admin console's configuration. Where you can, remove such a profile before users sign in, as described under [Migrate an existing fleet to the admin console](#migrate-an-existing-fleet-to-the-admin-console).

317369

318370To prevent the move, or to allow it only for your organization, see [Keep a device on its managed profile](#keep-a-device-on-its-managed-profile). Before Claude Desktop 2.37337.0, the device uses the profile and ignores the admin console.

319371

from line 422

370422 A device that left the admin console's configuration on an earlier release goes back too, so add `disableDeploymentModeChooser` to the profile before devices update. A key that you add later takes effect at the device's next launch.

371423</Warning>

372424

373Conversations created under the admin console's configuration stay on the device but no longer appear in the app's history after the device returns to the profile. Users can bring them into the app's history from **Settings → Import & export** in the app, as described at the end of [Start from an existing configuration file](#start-from-an-existing-configuration-file), after you set the [`claudeAiImport`](/docs/third-party/claude-desktop/configuration#claudeaiimport) key with `enabled` set to `true` in the profile or policy you deploy.

425Conversations created under the admin console's configuration stay on the device but no longer appear in the app's history after the device returns to the profile. Users can bring them into the app's history from **Settings → Import & export** in the app, as described under [Open the import wizard](/docs/third-party/claude-desktop/import#open-the-import-wizard), after you set the [`claudeAiImport`](/docs/third-party/claude-desktop/configuration#claudeaiimport) key with `enabled` set to `true` in the profile or policy you deploy.

374426

375427## Manage the configuration with the Admin API

376428