Skip to main content
Look up which Enterprise Admin Console settings Claude Code applies in the terminal and in VS Code, how it handles credentials and gateways, where data goes, and what the settings can’t prevent.

Console settings that Claude Code follows

This table shows the fields under Organization settings > Desktop 3P that Claude Code follows: If you block an MCP server that the developer added and that’s already running, the server keeps answering in that session.

Claude Code settings as JSON

The JSON on the Claude Code page has the same format as managed-settings.json, but Claude Code applies only a fixed list of its settings. No setting in the JSON can grant a permission, run a command, sign in, or choose a provider or a model. To enter the JSON, see Add Claude Code settings as JSON.

Settings that Claude Code applies

This table shows the main settings that Claude Code applies. For what each one does, see the settings reference. Claude Code ignores every setting that isn’t on its list, such as permissions.allow, model, hooks, forceLoginOrgUUID, requiredMinimumVersion, and cleanupPeriodDays. It also ignores a switch that loosens a limit, such as disableWorkflows: false. Some settings have conditions:
  • Sandbox settings: these apply when the sandbox is on. Your JSON can’t turn it on, but Allowed egress hosts, the computer’s managed settings, or a developer’s own settings can.
  • permissions.ask: if a developer sets sandbox.autoAllowBashIfSandboxed to true, a Bash rule with no pattern, such as Bash or Bash(*), stops asking for sandboxed commands. To keep the rule asking, set that key to false in your JSON.
  • A switch or a group with a value that Claude Code can’t read, such as "disableBypassPermissionsMode": "allow" in permissions: for most of these, Claude Code applies the strictest value. In this example, bypass permissions mode stays blocked for every developer until you correct the value.
  • A deny setting that isn’t a list, such as "deniedModels": 5: it denies nothing
  • A setting that a group’s policy also sets: in the JSON, lists such as permissions.deny add together, so a policy can’t remove an organization-wide deny rule. A single value, or the whole allowedMcpServers list, comes from the highest-ranked policy that sets it. A console field in a policy replaces the organization-wide value.

Credentials and gateways

While a terminal uses your connection, the developer’s own Claude login or API key doesn’t go to the gateway. Check these settings before developers sign in:
  • Helper script: Claude Code checks the Helper script on your Connection page before it runs it. To install it, see Install the helper for Claude Code in the terminal.
  • A gateway that Claude Code can’t use: Claude Code in the terminal doesn’t use your gateway if, for example, the Helper script doesn’t run on the computer, or the sign-in flow is broker and you haven’t allowed browser sign-in. /status in Claude Code names the setting. The session then uses the provider and the credentials that are set on the computer. These can be the developer’s own Claude login or API key, even when ANTHROPIC_BASE_URL on the computer is your gateway’s address. If nothing on the computer sets a provider, Claude Code doesn’t start. In that case, it doesn’t send prompts to the Anthropic API with the developer’s own login or key.
  • Gateway-managed Claude Code: if the console doesn’t show this switch, it’s off. With an identity provider, the switch changes nothing in a terminal. With Interactive sign-in and no identity provider, a provider that the developer or the computer set stays in use until the developer runs /login in Claude Code. After that, the session follows the gateway’s own settings, and none of your console settings apply. In that setup, on a computer whose forceLoginOrgUUID lists your organization, Claude Code doesn’t sign in to the gateway. It refuses prompts there unless the developer or the computer set a provider or ANTHROPIC_BASE_URL.

Managed settings beside the console

If you keep managed settings beside the console, this is how the two sets of settings combine while a developer is signed in:
  • Many settings persist: these include cloud credentials, proxy variables, model names, hooks, required versions, managed MCP servers, and plugins
  • Your connection replaces these env values: the cloud provider, region, project, resource, provider base URL, and custom request headers. If you have a Model list, it replaces availableModels.
  • These stop applying, and you can enter them in the console: sandbox.network.deniedDomains, sandbox.filesystem.denyRead, sandbox.filesystem.denyWrite, disabledMcpjsonServers, companyAnnouncements, and allowedMcpServers if you set it without allowManagedMcpServersOnly
  • These stop applying, and the console can’t set them: permissions.allow, the default permission mode, added directories, statusLine, and display preferences. The developer’s own settings decide these.
  • These apply together with your console settings: permissions.deny, permissions.ask, deniedModels, deniedMcpServers, blocked marketplaces, and Auto mode’s deny rules
  • The stricter value applies: switches that only restrict, such as permissions.disableBypassPermissionsMode, allowManagedHooksOnly, and sandbox.enabled

Managed settings that conflict with the console

Check the computer’s managed settings for these:
  • A private endpoint: the managed settings can point Claude Code at a private address for your provider, such as ANTHROPIC_BEDROCK_BASE_URL for a VPC endpoint. Your connection overrides that address, and requests go to the provider’s default address. To keep the private address, enter it in the provider’s base URL field on the Connection page, such as Bedrock base URL. Claude Desktop then uses that address. Claude Code in the terminal stops using your connection, and uses the provider, region, address, and credentials that are set on the computer. Your restrictions still apply, but your Model list and custom headers don’t. The base URL field applies to every developer who signs in, so Claude Code doesn’t start on a computer that sets no provider.
  • A Microsoft Foundry key: if the managed settings set ANTHROPIC_FOUNDRY_API_KEY or ANTHROPIC_FOUNDRY_AUTH_TOKEN, check which of these applies, and make the change in the managed settings. Don’t set both ANTHROPIC_FOUNDRY_RESOURCE and ANTHROPIC_FOUNDRY_BASE_URL, because Foundry requests then fail.
    • If they set ANTHROPIC_FOUNDRY_RESOURCE, or neither: make sure that ANTHROPIC_FOUNDRY_RESOURCE is set beside the Foundry key. Otherwise, Claude Code refuses each Foundry request once the computer has forceLoginOrgUUID, even before a sign-in. If your provider is Microsoft Foundry, use the resource on your Connection page. With any other resource, Claude Code refuses each Foundry request after a sign-in.
    • If they set ANTHROPIC_FOUNDRY_BASE_URL and your provider is Microsoft Foundry: a sign-in overrides that base URL, and Claude Code then refuses each Foundry request. Replace it with ANTHROPIC_FOUNDRY_RESOURCE, set to the resource on your Connection page. To keep it as a private endpoint instead, follow A private endpoint in this list.
  • forceLoginMethod and forceLoginGatewayUrl: remove forceLoginGatewayUrl, and don’t set forceLoginMethod to console or gateway. Otherwise, Claude Code refuses the sign-in to your organization.
  • allowedProviders: add your provider to the list. For a gateway, add customEndpoint, and set ANTHROPIC_BASE_URL in the managed env to your Gateway base URL, with a lower-case host and no trailing slash.
  • Model names: model, fallbackModel, and modelOverrides persist. If those model names are for a different provider than your connection, remove them.
  • A policy helper: the computer ignores your console, even with forceLoginOrgUUID
To go back, remove your organization’s ID from forceLoginOrgUUID, or remove forceLoginOrgUUID if yours is the only ID. Also remove enforceAnthropicSignIn and parentSettingsBehavior if you set them. Ask developers to run claude auth logout in their terminal, which removes the leftover sign-in and their other Claude Code logins.

Where data goes

While a terminal uses your connection, model requests and their content go from the developer’s terminal to your provider or gateway. For the sign-in and your settings, the terminal exchanges the following with Anthropic:
  • At sign-in: after the developer approves in their browser, Claude Code receives a token that can read the developer’s profile and the Claude Desktop configuration that applies to them, including your Connection settings. The token can’t run a model.
  • At each download: Claude Code sends that token to api.anthropic.com and receives the settings for that developer
  • To complete, renew, or end the sign-in: Claude Code sends the sign-in’s own tokens to platform.claude.com
Claude Code’s own telemetry includes the following:
  • Usage metrics: the sign-in itself sends some usage metrics to api.anthropic.com and to Datadog (http-intake.logs.us5.datadoghq.com), even with Block nonessential telemetry on, because Claude Code downloads that setting after the sign-in
  • Error reports: a session under your settings sends none
  • WebFetch domain check: a session sends each page’s host name to api.anthropic.com, unless you turn on Skip WebFetch domain check
Claude Code keeps these on the developer’s computer, among other files:
  • The sign-in, and the sign-in to your gateway: in Claude Code’s credential store. This is the Keychain on macOS, and the file .credentials.json in Claude Code’s configuration directory on Linux, or on macOS if the Keychain refuses the write. On Windows, it’s that file or Windows Credential Manager.
  • The stored copy of your settings: in Claude Code’s configuration directory, ~/.claude by default. It doesn’t hold your connection.
  • A record of where your connection sent requests: in ~/.claude.json. The record holds your organization’s ID and no credentials. For a cloud provider, it also holds the provider with its region, project, resource, AWS profile, and Amazon Bedrock inference profiles, which can include an AWS account ID. For a gateway, it holds the gateway’s host and your identity provider’s address.

Security considerations

A developer doesn’t need administrator access to bypass your settings. These are some of the ways a developer can work without them, and what limits each one:
  • Signs in to another organization that’s set up this way, on a computer with no managed settings: the other organization’s settings apply instead of yours. forceLoginOrgUUID in the computer’s managed settings limits this.
  • Signs in to your organization while still signed in to a Claude apps gateway, on a computer with no managed settings: sessions stay on that gateway, and your settings don’t apply. The sign-in then prints Claude Code still uses the gateway at. To fix it, the developer runs claude auth logout in their terminal and signs in to your organization again. If their own settings set forceLoginMethod to gateway, they first remove it and forceLoginGatewayUrl. forceLoginOrgUUID limits this. /status in Claude Code shows a session that follows a gateway’s own settings as Cloud gateway, and the Allow sign-in from Claude Code in terminals and IDEs switch doesn’t stop it.
  • Signs in with their own Claude account: Claude Code ends the organization sign-in and removes the stored copy of your settings. forceLoginOrgUUID limits this. On a computer that requires the sign-in, a claude.ai login still starts sessions on the Anthropic API, without your settings.
  • Changes how Claude Code starts on their own computer: the sign-in keys are checked on the developer’s computer. Sessions can run on the Anthropic API under another login, without your settings. allowedProviders without "anthropic" in the computer’s managed settings limits this, if developers don’t need direct access to the Anthropic API. Otherwise, only controls outside Claude Code limit this.
  • Runs claude mcp serve, which gives another program access to Claude Code’s tools: calls from that program skip your permission rules. The sandbox from Allowed egress hosts still applies. Only controls outside Claude Code limit this.
  • Installs a plugin that contains a mod, loads one with --plugin-dir, or has Claude write one: the mod runs code as the developer. Your deny rules, Disabled built-in tools, and Built-in tool policy don’t apply to actions of the mod itself. allowManagedHooksOnly set to true in your JSON limits this. It also stops developers’ own hooks, and hooks and mods in plugins that developers add, including plugins from your Plugin marketplaces.
  • Runs a version before 2.1.329: it ignores your settings and enforceAnthropicSignIn. requiredMinimumVersion in the computer’s managed settings limits this. Don’t set it on a computer that also runs Claude Desktop on your provider.
The sign-in keys and your own settings have limits too:
  • forceLoginOrgUUID: the check runs on the developer’s computer and isn’t a security boundary. It doesn’t check the organization of a Claude Console login or an Anthropic profile. Unless you also require the sign-in, both still work on the Anthropic API, and a saved Claude Console key also works at an ANTHROPIC_BASE_URL that the developer sets.
  • enforceAnthropicSignIn: it applies only when Claude Code can read the managed settings that set it. If you set no forceLoginOrgUUID, no session starts on a cloud provider or a custom base URL.
  • After a sign-in ends: on a cloud provider that the developer or the computer set, most restrictions in the stored copy, though not deniedModels, stay in force until the developer runs claude auth logout in their terminal or signs in with another account
  • Credential settings: AWS profile name, AWS config directory, GCP credentials file path, and Helper script on your Connection page can run a command on the developer’s computer, in some cases without asking the developer. Give the Owner role, and any other access to the Desktop 3P pages, only to people you trust to run programs there.
To enforce budgets and rate limits and to log each model request, use an LLM gateway.