Skip to main content

Plan identity and sign-in

A Claude Desktop on 3P deployment has several separate sign-ins, and most can use a different identity system. List them before you schedule your move. If you're also changing identity providers (IdPs), the order of the two projects matters, because by default claude.ai accepts one IdP at a time.

This guide is for admins of organizations on Claude Enterprise plans.

This article is part of Move from Claude Enterprise to Claude Desktop on a cloud provider, which defines the terms wave, overlap period, and cutoff date.

Sign-ins your users will see

Sign-in

Who sees it

What it uses

claude.ai (your Claude Enterprise organization)

Every user, until their last import. The import wizard opens claude.ai in the browser to sign in and authorize.

The SSO connection held by your parent organization.

Enterprise Admin Console

Only users whose app is managed from the console. With MDM, a local file, or a bootstrap server, users have no Anthropic account.

A Claude account under the user's work email, through your SSO if you connect it. SSO is recommended but not required. The sign-in expires about once a month.

Your provider

Every user, unless you deploy a shared key, a credentials file, or a credential helper.

IAM Identity Center, Google or Workforce Identity, or Entra ID. It's separate from the Claude sign-in, and the app never sends Claude credentials to your provider.

Bootstrap server

Only deployments that use one with per-user sign-in.

Your own IdP. It's independent of the inference sign-in, except in device-code mode, where one sign-in covers both if the gateway and the bootstrap server share an origin.

Connectors

Each user, once per connector.

The IdP of the connector's vendor. The app stores each connector token on the device, so users connect each one again in the new app.

Claude Code CLI

Developers.

The cloud provider's own credential chain. See Move Claude Code CLI users.

Connect your IdP to your cloud provider

Each provider's setup guide explains how to connect your IdP.

If you're changing IdPs

We recommend this order:

  1. Connect the new IdP to your cloud provider first, and pilot sign-in there. On AWS, if IAM Identity Center already uses the old IdP, this step replaces that organization's one identity source. You can't pilot the two side by side in the same AWS organization.

  2. If the old IdP will stay in service long enough, leave the claude.ai SSO connection alone until the last wave has imported.

  3. If the old IdP retires sooner, make the switch between waves. Don't switch while a wave is importing. Compare the email attributes in both IdPs first.

  4. Keep claude.ai sign-in and member data export working until the final import is done.

Settings for the overlap period

  • Sign-in screen: Users can choose claude.ai or your provider configuration. deploymentMode set to 3p hides the claude.ai option (Claude Desktop 4.16336.0 or later). Set it in a device profile that also sets your connection. For earlier versions, also set disableDeploymentModeChooser to true. You can't set either key in the console. Don't set them on a device the console manages, because they make the app stop using the console.

  • Organization lock: forceLoginOrgUUID limits standard sign-in on the device to your organization. It also accepts a list of organization IDs. With the console, include your Enterprise Admin Console organization's ID as well as your Claude Enterprise organization's, and update devices to 2.37337.0 or later first. Otherwise, the console's settings don't apply.

  • Network allowlist: Tenant Restrictions uses a header that lists allowed organization IDs. Make sure it includes every organization your users still sign in to.

  • Users in two organizations: A console user who also belongs to another organization is asked whether to switch, and each switch restarts the app. Turn on Require this organization in Claude Desktop so users can't dismiss the prompt. If your Claude Enterprise organization blocks other accounts in Claude Desktop, first add the Enterprise Admin Console organization's ID to its Allowed organizations list.

  • Claude Code CLI: List both providers in allowedProviders during the overlap period. CLAUDE_CONFIG_DIR gives each account its own configuration directory.

Did this answer your question?