Text of code.claude.com › docs › en › admin-setup as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Set up Claude Code for your organization - 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. Claude Code enforces organization policy through managed settings that take precedence over local developer configuration. You deliver those settings from the Claude admin console, your mobile device management (MDM) system, or a file on disk.

The settings control which tools, commands, servers, and network destinations Claude can reach. This page walks through the deployment decisions in order. Each row links to the section below and to the reference page for that area. SSO, SCIM provisioning, and seat assignment are configured at the Claude account level. See the Claude Enterprise Administrator Guide and seat assignment for those steps. Decision What you’re choosing Reference Choose your API provider Where Claude Code authenticates and how it’s billed Authentication , Amazon Bedrock , Google Cloud’s Agent Platform , Microsoft Foundry Decide how settings reach devices How managed policy reaches developer machines Server-managed settings , Delivery mechanisms Decide what to enforce Which tools, commands, and integrations are allowed Permissions , Sandboxing Set up usage visibility How you track spend and adoption Analytics , Monitoring , Costs Review data handling Data retention and compliance posture Data usage , Security Choose your API provider Claude Code connects to Claude through one of several API providers.

Your choice affects billing, authentication, which compliance posture you inherit, and which Claude Code features your developers can use. Provider Choose this when Claude for Teams / Enterprise You want Claude Code and claude.ai under one per-seat subscription with no infrastructure to run. This is the default recommendation. Claude Console You’re API-first or want pay-as-you-go billing Amazon Bedrock You want to inherit existing AWS compliance controls and billing Google Cloud’s Agent Platform You want to inherit existing GCP compliance controls and billing Microsoft Foundry You want to inherit existing Azure compliance controls and billing Some Claude Code features require a claude.ai account.

Cloud sessions , cloud scheduled tasks , Code Review , Remote Control , and the Chrome extension aren’t available through Console API keys or cloud-provider credentials alone. If you deploy through Amazon Bedrock, Google Cloud’s Agent Platform, or Microsoft Foundry, plan whether developers also need Claude for Teams or Enterprise seats. Each feature page lists its plan requirements. For the full provider comparison covering authentication, regions, and feature parity, see the enterprise deployment overview .

Each provider’s auth setup is in Authentication . Proxy and firewall requirements in Network configuration apply regardless of provider. If you want a single endpoint in front of multiple providers or centralized request logging, see LLM gateway . Decide how settings reach devices Managed settings define organization policy. Claude Code checks the four sources in the table below in priority order. How Claude Code combines managed sources says which of them apply, what a policy helper changes, and how to compose every source.

The table is the decision map. Mechanism Delivery Priority Platforms Server-managed claude.ai admin console, or a self-hosted Claude apps gateway for gateway sign-ins Highest All plist / registry policy macOS: com.anthropic.claudecode plist Windows: HKLM\SOFTWARE\Policies\ClaudeCode High macOS, Windows File-based managed macOS: /Library/Application Support/ClaudeCode/managed-settings.json Linux and WSL: /etc/claude-code/managed-settings.json Windows: C:\Program Files\ClaudeCode\managed-settings.json Medium All Windows user registry HKCU\SOFTWARE\Policies\ClaudeCode Lowest Windows only Claude Code fetches server-managed settings at startup and refreshes them hourly during the session, with no endpoint infrastructure to deploy.

Delivery through the claude.ai admin console requires a Claude for Teams or Enterprise plan. Deployments on Amazon Bedrock, Google Cloud’s Agent Platform, or Microsoft Foundry can get the same remote delivery by running a Claude apps gateway , or use one of the file-based or OS-level mechanisms instead. If your organization mixes providers, configure server-managed settings for claude.ai users plus a file-based or plist/registry fallback so other users still receive managed policy.

The plist and HKLM registry locations work with any provider and resist tampering because they require admin privileges to write. The Windows user registry at HKCU is writable without elevation, so treat it as a convenience default rather than an enforcement channel. By default, WSL reads only the Linux file path at /etc/claude-code . To extend your Windows registry and C:\Program Files\ClaudeCode policy to WSL on the same machine, set wslInheritsWindowsSettings: true in either of those admin-only Windows sources.

Whichever mechanism you choose, managed values take precedence over user and project settings, apart from a few security-sensitive exceptions . Array settings such as permissions.allow and permissions.deny merge entries from lower-precedence settings into the managed settings that apply , so developers can extend managed lists but not remove from them. For fallbackModel , availableModels , and modelPicker , the managed value replaces lower layers rather than merging.

WSL sessions in Claude Code Desktop On Windows, Claude Code Desktop can run Code sessions inside a WSL 2 distribution . The session’s Claude Code process runs inside the distribution, so it resolves managed settings through the WSL discovery path above: Windows-only sources don’t reach it unless wslInheritsWindowsSettings: true is deployed. Claude Desktop turns off WSL sessions by default on devices it detects as organization-managed, for example when C:\Program Files\ClaudeCode\managed-settings.json exists.

To turn them on, deploy a Windows registry policy, which requires Claude Desktop v1.19367.0 or later: Create a value named disableWslSessions under HKLM\SOFTWARE\Policies\Claude and set it to the REG_SZ string false or the REG_DWORD 0 . This value sits under the Claude Desktop policy key, separate from the ClaudeCode key that carries managed settings. Deploy the value under HKLM, which requires administrator privileges to write.

A value under HKCU doesn’t enable WSL sessions. Leave C:\Program Files\ClaudeCode\managed-settings.json in place if you deploy it. Once disableWslSessions is false under HKLM, Desktop allows WSL sessions even though that file is present. Desktop reads the policy each time a WSL session starts, so you don’t need to restart the app after deploying it. If a device still refuses WSL sessions, open Help > Troubleshooting > Show Logs in File Explorer in Claude Desktop on that device, which saves a copy of its log folder to Downloads.

Search main.log in that copy for [wslPolicyGate] denying WSL session . The reason for the denial follows in parentheses, such as (cli-file-present) . After WSL sessions are enabled, extend your managed settings to them: Deploy wslInheritsWindowsSettings: true through the HKLM registry or the C:\Program Files\ClaudeCode file so WSL sessions inherit the same policy as host sessions. Verify by running /status inside a WSL session and reading the Setting sources line.

To interpret what it lists, see Read the source in /status . If a WSL session starts on a device with Claude Desktop’s allowedWorkspaceFolders list, a ~ entry means the home directory inside the distribution. Processes inside the WSL 2 utility VM aren’t visible to Windows-side endpoint detection sensors. To observe in-distro process and file activity, check your endpoint detection vendor’s WSL guidance for a Linux sensor you can run inside the distribution and the exclus

The rest of this page is on the live site.