Enterprise configuration

Organizations on Team or Enterprise plans can manage desktop app behavior through admin console controls, managed settings files, and device management policies.

Admin console controls

These settings are configured through the admin settings console:

• Code in the desktop: control whether users in your organization can access Claude Code in the desktop app
• Code in the web: enable or disable web sessions for your organization
• Remote Control: enable or disable Remote Control for your organization
• Disable Bypass permissions mode: prevent users in your organization from enabling bypass permissions mode

Managed settings

Managed settings override project and user settings and apply to Claude Code sessions in Desktop. You can set these keys in your organization's managed settings file or push them remotely through the admin console.

Key	Description
permissions.disableBypassPermissionsMode	set to "disable" to prevent users from enabling Bypass permissions mode.
disableAutoMode	set to "disable" to remove Auto mode from the mode selector. Also accepted under permissions.
autoMode	customize what the auto mode classifier trusts and blocks across your organization. See Configure auto mode.
browserExternalPageTools	set to "disabled" to prevent Claude from using tools to read or act on external pages in the Browser pane. Users can still navigate to external sites themselves, and local dev server previews are unaffected.
disableMobileSimulatorTools	set to true to block Claude's tools for controlling and capturing devices in the iOS Simulator pane. The pane stays usable for the user's own taps; only Claude's access is removed.
disableBrowserExternalNavigation	set to true to turn off external browsing in the Browser pane entirely. Neither users nor Claude can navigate to external sites, and localhost dev server previews are unaffected. The value must be the JSON boolean true; the string "true" is ignored.
sshConfigs	pre-configure SSH connections that appear in the environment dropdown. Users cannot edit or delete managed connections.
sshHostAllowlist	restrict SSH sessions to hosts whose resolved hostname matches one of these patterns. An empty array disables SSH sessions. Read from managed settings only.
disableDesktopLocalSessions	set to true to turn off Code sessions that run on the device, leaving SSH sessions to other hosts and cloud sessions available. The value must be the JSON boolean true. Read from managed settings only. Requires Claude Desktop v1.37937.0 or later.
managedMcpServers	push MCP server configurations to all users. Available in third-party (3P) Desktop deployments only. In each entry, set a transport of "http", "sse", or "stdio", connection details, and optionally a toolPolicy map to restrict which of that server's tools users can invoke. Deliver it through the managed settings file, MDM, or a Claude apps gateway policy's desktop block, since 3P deployments don't receive admin-console settings. To deliver it through the gateway, you need Claude Code v2.1.232 or later on the gateway server. This is the desktop app's own key; Claude Code reads a same-named managed setting of its own, with a different entry shape.

Which managed settings reach a Desktop session depends on where that session runs. Model restrictions such as availableModels are enforced in Desktop's Claude Code sessions the same way as in the terminal CLI; see surface coverage.

• Local sessions on this machine: a managed settings file deployed to disk applies. Managed settings pushed remotely through the admin console also reach these sessions on Anthropic's API when the session authenticates with an eligible login or key, following the same settings precedence as the terminal CLI.
• Cloud sessions: receive server-managed settings; device-deployed files don't reach them, because they run on Anthropic-managed VMs. Sessions routed to a self-hosted environment also read the managed settings file in the runner image. How Claude Code combines managed sources says when that file applies.
• SSH sessions: the session reads the managed settings file from the remote host. Desktop itself reads sshConfigs, sshHostAllowlist, and disableDesktopLocalSessions from the local machine's managed settings.
• Cowork sessions: in a Cowork session on this machine, Claude Code never fetches admin-console settings, even when the user signs in with a Team or Enterprise account, and reads policy deployed to the machine unless your Claude Desktop configuration sets requireCoworkFullVmSandbox. Remote Cowork sessions receive neither. See where and when a policy applies for which device files reach Cowork, and MCP permission rules for how Bash and WebFetch rules apply to Cowork's tools.

In local and SSH sessions, the desktop app delivers each user's connected claude.ai connectors to Claude Code directly. No MCP setting or managed-mcp.json reaches those connectors, whichever settings source or file location you use. To block a connector's tools in these sessions, use your organization's connector tool controls. How connectors reach Claude Code shows which settings govern connectors in each kind of session.

permissions.disableBypassPermissionsMode and disableAutoMode also work in user and project settings, but placing them in managed settings prevents users from overriding them.

For the permission, plugin, and delivery keys only a managed source can set, see Keys only managed settings can set.

Device management policies

IT teams can manage the desktop app through MDM on macOS or group policy on Windows. Available policies include enabling or disabling the Claude Code feature, controlling auto-updates, and setting a custom deployment URL.

• macOS: configure via com.anthropic.claudefordesktop preference domain using tools like Jamf or Kandji
• Windows: configure via registry at SOFTWARE\Policies\Claude

Network access requirements

Desktop loads its application code and user content from Anthropic CDN hosts.

anthropic.com
*.anthropic.com
claude.ai
*.claude.ai
claude.com
*.claude.com
claude.app
*.claude.app
*.claudeusercontent.com
*.claudemcpcontent.com

Traffic is HTTPS on port 443 unless you configure a custom port for OTLP, an LLM gateway, or an MCP server.

For proxy servers, custom certificate authorities, mTLS, and the domains the standalone CLI needs, see network configuration.

To reduce the number of firewall wildcards, allow these Anthropic hosts instead. Certain subdomains are dynamically generated and must remain wildcards.

anthropic.com
api.anthropic.com
a-api.anthropic.com
a-cdn.anthropic.com
s-cdn.anthropic.com
assets-proxy.anthropic.com
claude.ai
a.claude.ai
a-cdn.claude.ai
assets.claude.ai
downloads.claude.ai
*.livepreview.claude.ai
claude.com
platform.claude.com
*.livepreview.claude.app
*.claudeusercontent.com
*.claudemcpcontent.com

If your organization has IP allowlisting enabled for Claude, route bridge.claudeusercontent.com through the same proxy egress as claude.ai and api.anthropic.com. If you can't route it that way, add the egress address your proxy uses for that host to your organization's IP allowlist, but only when that address is dedicated to your organization: a shared proxy egress range also admits the proxy vendor's other customers.

Anthropic checks connections to that host against your organization's IP allowlist using the address they arrive from. If your proxy sends traffic for it out through an address that isn't on that allowlist, Claude in Chrome and other features that connect through the bridge stop working while the rest of the app keeps working.

An artifact that loads a typeface from Google Fonts also requests fonts.googleapis.com and fonts.gstatic.com. Both hosts are optional. If you block them, artifacts render in fallback typefaces. Block with a fast rejection rather than a silent drop so the font request fails immediately instead of delaying the page's first render.

Artifacts can also load JavaScript libraries, such as React or a charting package, from cdnjs.cloudflare.com, cdn.jsdelivr.net, cdn.tailwindcss.com, and code.jquery.com, and from no other external host. If you block those hosts, the parts of an artifact that depend on a library don't work, and unlike a blocked font, a blocked library has no fallback. Block with a fast rejection here too, so a blocked library request fails at once rather than hanging until it times out.

Authentication and SSO

Enterprise organizations can require SSO for all users. See authentication for plan-level details and Setting up SSO for SAML configuration; OIDC setup is covered in the Claude Enterprise Administrator Guide.

Data handling

Claude Code processes your code locally in local sessions, or in cloud sessions on Anthropic-managed infrastructure, unless your organization routes them to a self-hosted environment. Cloud sessions, including in a self-hosted environment, send conversations and code context to Anthropic's API for processing; local and SSH sessions send them to whichever model provider your deployment configures, Anthropic's API by default. See data handling for details on data retention, privacy, and compliance.

Deployment

Desktop can be distributed through enterprise deployment tools:

• macOS: distribute via MDM such as Jamf or Kandji using the .dmg installer
• Windows: deploy via the MSIX package. See Deploy Claude Desktop for Windows for enterprise deployment options including silent installation

For the domains to allowlist in your firewall, see network access requirements above. For proxy settings, custom certificate authorities, and LLM gateways, see network configuration.

For the full enterprise configuration reference, see the enterprise configuration guide.