Configure server-managed settings - Claude Code Docs
Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. Server-managed settings let organization Owners centrally configure Claude Code from Organization settings > Claude Code > Managed settings in the claude.ai console. Claude Code clients fetch these settings automatically when users authenticate with an eligible credential on a platform where server-managed delivery is supported.
See Platform availability for the credentials and platforms that qualify. Server-managed settings are available for Claude for Teams and Claude for Enterprise customers. Requirements To use server-managed settings, you need: Claude for Teams or Claude for Enterprise plan The Owner or Primary Owner role in your Claude organization, to view and edit the configuration Network access to api.anthropic.com Choose between server-managed and endpoint-managed settings Claude Code supports two approaches for centralized configuration.
Server-managed settings deliver configuration from Anthropic’s servers. Endpoint-managed settings are deployed directly to devices through native OS policies (macOS managed preferences, Windows registry) or managed settings files. Approach Best for Security model Server-managed settings Organizations without MDM, or users on unmanaged devices Settings that Claude Code fetches from Anthropic’s servers at startup and refreshes hourly during the session Endpoint-managed settings Organizations with MDM or endpoint management Settings deployed to devices via MDM configuration profiles, registry policies, or managed settings files If your devices are enrolled in an MDM or endpoint management solution, endpoint-managed settings provide stronger security guarantees because the settings file can be protected from user modification at the OS level.
Endpoint-managed settings don’t reach cloud sessions in Anthropic-hosted environments, so organizations whose developers run cloud sessions should configure server-managed settings as well. Sessions in a self-hosted environment also read the managed settings file in the runner image. The settings precedence below says when that file applies. Configure server-managed settings 1 Open the admin console In the claude.ai console, go to Organization settings > Claude Code > Managed settings .
In a Team or Enterprise organization, if the page says you don’t have access, ask an Owner or Primary Owner to make the change. 2 Define your settings Add your configuration as JSON. All settings available in settings.json are supported except those restricted to OS-level policy delivery; see Current limitations for that short list. This includes hooks , environment variables , and managed-only settings like allowManagedPermissionRulesOnly .
This example enforces a permission deny list, prevents users from bypassing permissions, and restricts permission rules to those defined in managed settings. The Bash(curl *) rule matches curl as Claude writes it , not /usr/bin/curl or sh -c 'curl …' ; for network enforcement that doesn’t depend on the command text, add a sandbox block with allowManagedDomainsOnly . { "permissions" : { "deny" : [ "Bash(curl *)" , "Read(./.env)" , "Read(./.env.*)" , "Read(./secrets/**)" ], "disableBypassPermissionsMode" : "disable" }, "allowManagedPermissionRulesOnly" : true } Hooks use the same format as in settings.json .
This example runs an audit script after Edit and Write tool calls across the organization: { "hooks" : { "PostToolUse" : [ { "matcher" : "Edit|Write" , "hooks" : [ { "type" : "command" , "command" : "/usr/local/bin/audit-edit.sh" } ] } ] } } Because hooks execute shell commands, users in interactive sessions see a security approval dialog before Claude Code applies them. To configure the auto mode classifier so it knows which repos, buckets, and domains your organization trusts, deliver an autoMode block the same way; see Configure auto mode for how the autoMode entries affect what the classifier blocks and important warnings about the environment , allow , soft_deny , and hard_deny fields.
3 Save and deploy Save your changes. Claude Code clients receive the updated settings on their next startup or hourly polling cycle. The editor checks your JSON against the published JSON schema for Claude Code settings. If it finds a problem in JSON that parses, it shows a warning and relabels the save button. The label is Update with errors when settings are already saved, and Add with errors when no settings are saved yet.
That button still saves, because a schema warning doesn’t block the save. The schema can lag behind the newest releases , so the editor can flag a key or value that the settings reference documents. Claude Code receives the keys and values you saved and runs its own validation when it loads them. Verify settings delivery To confirm that settings are being applied, ask a user to restart Claude Code. If the configuration includes settings that trigger the security approval dialog , the user sees a prompt describing the managed settings the next time Claude Code fetches them: at the next start, or within an hour in a running interactive session.
You can also verify that managed permission rules are active by having a user run /permissions to view their effective permission rules. In a session, have the user run /status . The Setting sources line lists Enterprise managed settings with remote in parentheses when server-managed settings apply. To check the fetch outcome on a specific machine, have the user run claude doctor and read the Managed settings (remote) line.
Requires Claude Code v2.1.248 or later. The line reports one of four outcomes: The delivered settings loaded Your organization has no server-managed settings configured The fetch failed, with the cause and whether a cached policy still applies Claude Code skipped the fetch, with the reason. See Platform availability for the providers and configurations that skip it While the fetch is still in progress, the line reports that instead.
In a running session, /status shows the same line after a failed fetch, and for some skipped-fetch causes, such as a third-party provider variable or a custom ANTHROPIC_BASE_URL exported in the user’s shell. Give groups different settings On an Enterprise plan, you can give each group of members its own configuration instead of one organization-wide configuration. If your organization has HIPAA enabled , group configurations aren’t available yet.
Each group must already exist, either synced from your identity provider through SCIM or as a custom group you manage in the admin console. Each member receives at most one configuration, the same on every device: A member of a group with a configuration : the configuration ranked highest among their groups Anyone else , including a member whose only group with a configuration was deleted: the catch-all configuration, if you set one Configurations don’t merge with each other or with the organization-wide configuration, so each one must hold every setting you want that group to have.
To apply a restriction to every member, put it in every group configuration and in the catch-all. Members keep receiving the organization-wide configuration until the last of these steps, so you can set up and test everything first: 1 Add a configuration for each group In Organization settings > Claude Code > Managed settings , click Add configuration , pick the group, and choose a starting point. To loosen policy for a group, pick a group that your identity provider syncs, so that no one can add themselves to it in the admin console.
To keep what members have today and change a few settings, start from a copy of your organization-wide configuration. Edit the configuration and save it. 2 Set the catch-all Click Set on Everyone else and add the JSON for members who match no grou
The rest of this page is on the live site.