1. Build a configuration in the app
Launch Claude Desktop. Do not sign in or create an Anthropic account; stay on the login screen. From the macOS menu bar (or on Windows and Linux, the application menu ☰ in the top-left of the login screen), go to Help → Troubleshooting → Enable Developer Mode, then Developer → Configure Third-Party Inference… to open the in-app configuration window. The window is organized into sections in the left sidebar. Work through them in order; each maps to a group of configuration keys, and the window validates values as you enter them. Unified Claude is on by default in current versions of Claude Desktop, even where your profile setschatTabEnabled, chatAdvancedFileAnalysisEnabled, or coworkTabEnabled to false.
When a managed (MDM-delivered) configuration is already present on the device, the configuration window opens read-only: it shows what the admin deployed, marks the configuration as organization-managed, and directs users to their IT administrator. To author a new configuration, use a device without a managed profile, or temporarily remove the profile. Profiles that set only the app-behavior keys and the keys treated like them leave the window editable.
2. Export the profile
Once your configuration tests successfully, click Export and choose a format:
Apply Changes and Export do different things:
- Apply Changes asks you to confirm, then writes the selected configuration to your own machine’s Claude settings and relaunches the app, so you can test it end to end before deploying it.
- Export writes a deployment file in the format you choose and leaves your local settings untouched.
Export a configuration template
A configuration template lists the settings that your device management tool can set for Claude Desktop, and holds no values. Export one when you enter values in your management console or profile editor and don’t build a configuration in the app. From the macOS menu bar (or on Windows and Linux, the application menu ☰ in the top-left of the sign-in screen), go to Help → Troubleshooting → Enable Developer Mode, then Developer → Export Configuration Template…. Every checkbox is selected when the window opens. Clear what you don’t need, then export and pick where to save the file:- Settings to include: Standard Claude Desktop is for devices that use Anthropic’s models through claude.ai, and Third-party inference is for devices that use your organization’s inference provider. Keep both for a fleet with both kinds of device, so that one template covers them all. A setting’s help text says when the setting applies in one mode only, or when setting it opens Claude Desktop in third-party mode.
- Format: Group Policy template (ADMX) saves
Claude-ADMX.zip, which holdsClaude.admxanden-US/Claude.adml. Profile Manifest (.plist) savescom.anthropic.claudefordesktop.plist. With both selected, you getClaude-Configuration-Templates.zip, which holds all three files.
- Group Policy central store: overwrite
Claude.admxanden-US\Claude.adml - Intune: note the values and assignments in the profiles that use the earlier import, delete those profiles, delete that import, import the new files, then create the profiles again, as in Microsoft’s Replace existing ADMX files. Until the new profiles reach a device, Intune doesn’t enforce your Claude settings there.
Creating profiles for multiple user groups
Many organizations deploy distinct configurations to different populations: for example, a permissive profile for an engineering pilot group and a restricted profile for the broader rollout, or per-region profiles that point at different inference endpoints. The configuration window can hold multiple named configurations. Use the picker in the top-right of the window:- New configuration creates an empty configuration.
- Duplicate copies the current configuration as a starting point for a variant.
- Rename and Delete manage the list.
- Reveal in Finder (Show in Explorer on Windows, Show in file manager on Linux) opens the folder where saved configurations are stored. Don’t set up another device or user account from a copy of these files (see Unreadable saved API keys). To use a configuration on another device, click Export.
On macOS, check whether your assignment rules install a profile for the whole computer (a machine profile) or for one user account (a user profile). Give each Mac one machine profile with every key in it; see Deploy the configuration. To vary configuration between groups on macOS, scope machine profiles to device groups, or serve per-user configuration from a bootstrap server.On Windows, check which registry hive your assignment rules write to. If your assignment rules deliver a profile in user context, it lands in user policy (
HKCU), and the app ignores user policy entirely when machine policy is present; see Deploy the configuration. To vary configuration per user group on Windows, deliver every profile through user policy and keep HKLM\SOFTWARE\Policies\Claude empty, or serve per-user configuration from a bootstrap server.Before you deliver an exported .reg file through user policy, make sure the registry path in the file starts with HKEY_CURRENT_USER, not HKEY_LOCAL_MACHINE.3. Allow required network egress
The hosts the app needs to reach depend on the configuration you built: your inference provider’s endpoint is always required, and each telemetry, update, and service setting you leave enabled adds its own hosts. The configuration window shows the exact allowlist for your settings and can export it as a text file for your network team. Open these hosts on your perimeter firewall before rolling out to devices. See Telemetry and egress for the full list of hosts grouped by the setting that controls each one, and for the distinction between the perimeter firewall and the in-app sandbox allowlist.4. Deploy the configuration
Push the exported configuration through your MDM. On macOS and Windows, put all of a device’s managed keys in one location, preferably the machine location. To vary configuration per user group, see Creating profiles for multiple user groups. The app reads from these locations:- macOS
- Windows
- Linux
A
.mobileconfig profile delivered by MDM lands in the Managed Preferences locations automatically. A profile that your MDM installs for the whole computer is a machine profile, and a profile that it installs for one user account is a user profile. Some MDMs call these computer level and user level.- Deploy one machine profile to each Mac: put the complete configuration in it. If a Mac also has a user profile for the app, copy the keys that you still need into the machine profile, then remove the user profile. Before you upload an exported
.mobileconfigfile, check that itsPayloadScopeisSystem, and change it if it isn’t. - Leave profile installation to your MDM: set Apple’s
allowUIConfigurationProfileInstallationrestriction tofalse. The restriction applies on macOS 13 and later, and also stops users from installing certificates by hand.
configLibrary/ are ignored.
Restrict a device to one deployment mode
Claude Desktop on 3P runs on the inference provider or bootstrap server in your configuration. In standard Claude Desktop, users sign in to claude.ai. To stop users from switching a device between the two, setdeploymentMode in the managed source:
3p: the app uses the connection that the managed source sets, such as an inference provider or bootstrap keys. The sign-in screen doesn’t offer Or sign in with Claude.ai. With nothing to connect to in the same managed source, the app opens standard Claude Desktop, so set a connection there to keep users from signing in to claude.ai.1p: the app always runs as standard Claude Desktop and ignores inference provider and bootstrap keys.any: the same as leaving the key unset. Where users can switch, the two modes share some data on the device.
3p or 1p, a user can’t move the device to an Enterprise Admin Console organization, and the app doesn’t offer or accept the Claude API account sign-in. To allow the move only to your organization, set forceLoginOrgUUID instead. The app ignores deploymentMode in a bootstrap response. It treats a misspelled value as 3p.
deploymentMode requires Claude Desktop 4.16336.0 or later. Earlier versions read disableDeploymentModeChooser, and later ones still read it, so an existing profile works as before. On a device without a bootstrap server, disableDeploymentModeChooser set to true in a managed source does what 3p does, unless deploymentMode is 1p. On a device with a bootstrap server, the response replaces the profile’s disableDeploymentModeChooser, so set deploymentMode to 3p in the profile to restrict that device.
While a fleet updates to 4.16336.0, plan for these cases:
- A profile that gains
3p, or gains1pand sets nothing to connect to: also setdisableDeploymentModeChoosertotrueuntil every device has updated. On a device with a bootstrap server, set it in the response too. If a profile that you export from the in-app configuration window doesn’t setdisableDeploymentModeChoosertotrue, add the key to the exported file. - The Linux file: an earlier version treats
deploymentModeas a key that it doesn’t recognize (see Keys that an earlier version does not recognize), so add it to a device’s file after that device updates.
Update keys and managed precedence
A small group of app-behavior keys is treated specially, so you can set an update policy, a restart window, or a network proxy from MDM without managing the whole configuration:- The update keys
disableAutoUpdates,autoUpdaterEnforcementHours,installedUpdateEnforcementEnabled,installedUpdateEnforcementHours,updateViaUpdatesHost, andreleaseChannel. - The configuration lifecycle keys
relaunchEnforcementHoursandconfigRecheckIntervalMinutes. - The network proxy keys
egressProxyUrlandegressProxyPacUrl. See Network proxy. - The Code session keys
disableWslSessionsandclaudeCodeProcessWrapperEnabled. See Start Code sessions through a corporate launcher.
relaunchEnforcementHours or configRecheckIntervalMinutes therefore runs their defaults (24 hours and 10 minutes) on those devices, so set them in the same profile when you want other values.
A profile of only these keys leaves what the device connects to in the local configuration, which a user can edit. If that connection runs every session on a server and none on the device, that server answers the device’s update checks, so the app installs only the updates that the server offers. Update, restart, and re-check timing then comes from that server or takes its default, and most of these keys stop applying, the network proxy keys among them, though disableAutoUpdates still applies. To prevent this, set the connection in the profile, or set deploymentMode to 1p on a device that only signs in to claude.ai.
organizationAnnouncement, deploymentLogo (the logo shown beside the announcement), and remoteFileDownloads aren’t in the group. A profile that sets one or more of them, alone or beside keys from the group, also leaves the locally authored configuration in force. Such a profile still changes behaviors on the device (see What a profile or policy changes on a device). Update devices before you add one of these keys (see Keys that an earlier version does not recognize). For a profile that also sets bootstrapUrl, see Which configuration source applies on a device.
What a profile or policy changes on a device
A profile or policy for Claude Desktop, even one that leaves the local configuration in place, changes these behaviors on the device, among others:- Sessions in Windows Subsystem for Linux (WSL): Claude Desktop refuses them unless machine policy (
HKLM) setsdisableWslSessionstofalse. A per-userfalsedoesn’t count.disableWslSessionsis an app-behavior key, so put the app-behavior keys that you use in the same policy. - Shell commands in Code sessions: Claude Code’s sandbox turns on where it can run, and shell commands reach no host (see Unset allowlist in Code sessions). This happens where the profile leaves the local configuration in place and the user left Allowed egress hosts at Not set. Have the user add the hosts that shell commands need under Capabilities > Allowed egress hosts in the in-app configuration window. A profile that holds the whole configuration sets the hosts itself, in
coworkEgressAllowedHosts. - File downloads from an SSH host or WSL: an unset
remoteFileDownloadsmeanslimitedon the device. In Claude Desktop 6.6395.0 or later, an unset key meansallon a device where Claude Desktop finds no profile, policy, or other sign of an administrator. coworkEgressAllowedHostsin the profile: keepcoworkEgressAllowedHostsout of a profile or policy that doesn’t set a connection. With that key and without a connection, the profile replaces the user’s configuration, and Claude Desktop starts with nothing to connect to.
Keys that an earlier version does not recognize
Update a device before you add a key that its version of Claude Desktop doesn’t recognize. What that version does with the key differs by platform:- Windows: a machine policy (
HKLM) that holds only keys that the version doesn’t recognize turns off the settings from the in-app configuration window, the Enterprise Admin Console, or a bootstrap server. That includes the connection. Beside a key that the version recognizes, Claude Desktop ignores the unrecognized key. - Linux: an unrecognized key in
/etc/claude-desktop/managed-settings.jsonturns off the same settings when the file holds no other key, or only the app-behavior keys and the keys treated like them. Where the file also sets a connection, the file still applies, but a device that uses the Enterprise Admin Console goes back to the file’s settings at its next launch, and features that need every key of the file read, such as automatic deletion of idle sessions, can stay off. - macOS: Claude Desktop doesn’t see the key and keeps its settings. The profile still counts as a profile (see What a profile or policy changes on a device).