Guides/Playbook

Claude computer use reaches Enterprise: Stage access before rollout

8 min read
On this page
A desktop cursor reaches a document beyond a connected-folder boundary through an allowed application

Claude computer-use rollout

General Analysis

On November 20, 2026, Anthropic opened computer use in beta to Team and Enterprise plans. Claude can now see a user's screen and work in permitted desktop apps through the unified Claude experience. The rollout is gradual and the organization setting starts off.

An approved desktop app can reach files beyond the folders connected to Claude. Anthropic explicitly says folder restrictions and the folder Read only setting do not constrain computer use. There is no sandbox between Claude and the user's applications.

Prepare the pilot's exclusions before enabling the feature. Then verify the policy on a device, including how to withdraw access. This guide joins the documented controls into a proposed rollout procedure; General Analysis has not tested the beta in a customer tenant. For the surrounding endpoint and data-movement controls, see how to secure Claude Cowork.

Confirm which experience you are enabling#

This Team/Enterprise beta works in the new unified experience with Chat and Cowork unified enabled. Anthropic supports Claude Desktop on macOS 14 or later and Windows. Web and mobile use also require the organization's separate Computer access setting and an open Claude Desktop on the connected computer. It does not work in Claude Code or tasks started through the separate Cowork option. See the availability requirements.

Organizations with the HIPAA-ready configuration, ZDR for Claude Code, customer-managed encryption keys, or FERPA/K-12 settings cannot enable it. A missing toggle may simply mean the rollout has not reached the organization. Check eligibility before changing any controls.

Keep the two settings distinct: Computer use permits screen interaction; Computer access lets a remote or scheduled workflow reach the computer. Decide whether the pilot needs both. The Chat–Cowork migration guide covers the broader account transition and its scheduled-work implications.

See how your AI systems hold up under real attacks

General Analysis maps AI applications and agents, red teams prompts, retrieval, tools, MCP servers, browser actions, permissions, and business workflows, then turns findings into evidence your team can reproduce and retest.

Stage excluded roles before turning it on#

An Owner or Primary Owner enables Computer use under Organization settings → Capabilities → Claude Desktop. On Team, the setting covers all users because custom roles are unavailable. A Team pilot therefore needs another way to keep excluded devices off, such as the device policy below.

Enterprise administrators need to prepare both kinds of role exclusion. Anthropic's role instructions say users in built-in User, Admin, Owner, and Primary Owner roles gain access when the capability is enabled. Move people who should remain excluded to Custom roles and wait 15 minutes before enabling it.

For a custom role set to All capabilities, first change Capability access to Only selected and turn off Computer use. Wait 15 minutes. During organization enablement, clear every excluded custom role from the role list; those roles are usually selected already. Permitted custom roles also need the unified Chat and Cowork capability.

Suppose you want a ten-person pilot. Prepare the excluded users' role assignments first, then inspect an included and an excluded account on their actual devices. Selecting ten users does not limit access to ten if everyone else keeps a built-in role.

Verify app identity and reachable data#

Under App access, an owner can block named apps or allow only named apps. Users must still approve each permitted app. Anthropic's app-list instructions distinguish an unused empty allowlist from an active one: the list takes effect when its first app is added; removing the last app from an active allowlist denies all apps. Older Desktop clients lose computer use while an allowlist is active until they update.

Check the actual program identity. macOS uses bundle IDs. Windows accepts program filenames or Microsoft Store AUMIDs, and a launcher may have a different name from the process that owns the window. Anthropic gives LibreOffice's soffice.bin as an example. Typed IDs are not validated, and an app update can change an ID.

Use Anthropic's documented check: wait a minute after an app-list change, fully quit and reopen Desktop, then ask for the exact app in a new chat. Record the observed denial. Do not rely solely on that result for Windows apps with separate launcher and window processes.

Consider a pilot that allows a document editor. That editor may open files outside the connected work folder. Check which files its signed-in user can reach and where the task may put their contents before treating the workflow as read-only.

The documented exclusions include websites and browser extensions inside an approved browser, apps inside an approved remote desktop or VM window, indirect effects through approved apps, and text copied from a denied app. Record a skill can capture denied apps; Windows notifications from denied apps can remain visible. Other Claude tools and personal or other-organization accounts have separate boundaries.

That separation also appears in Anthropic's unified Enterprise control map: sandbox egress governs code in the sandbox, while connector policies govern connector calls. Neither setting establishes what an allowed native app can do.

Prepare the device-level off switch#

Anthropic's Desktop configuration reference provides computerUseEnabled. Set it to false at the computer level to keep computer use off for every account on that computer. It requires Claude Desktop 5.1231.0 or later. Setting it to true does not enable the feature or bypass user approval.

Upgrade before distributing the key. The deployment instructions warn that an older Windows client can reject the whole machine policy when it contains no recognized setting, and then ignore settings saved in the app, including a third-party inference setup.

On macOS, merge this dictionary entry into a computer-level configuration profile for com.anthropic.claudefordesktop. This is an excerpt, not a complete installable profile; use your MDM's profile editor and preserve existing settings.

Code source: Anthropic's computer-use MDM instructions.

XML
<key>computerUseEnabled</key> <false/>

On Windows, the corresponding value is a DWORD named computerUseEnabled, set to 0 under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Claude.

Review the rest of the policy before adding that first machine setting. On Windows, any value in the machine policy causes Desktop to stop reading the user-level Claude policy. On macOS, a computer-level profile takes precedence over user-level profiles for the domain. Move the other required settings into the computer-level policy as part of the same reviewed change.

Adding a policy key also changes other Desktop behavior. Anthropic's configuration reference says it hides the release-channel choice and makes the device follow Stable. The computer-use instructions say managed Windows devices refuse Code-tab WSL sessions unless machine policy explicitly sets disableWslSessions to false. Include those changes in the deployment review; decide separately whether WSL should remain available.

Desktop reads the off switch at startup. Fully quit and reopen the app, then inspect Enable computer use: it should be disabled with an organization-policy explanation. Closing the window is insufficient. An unreadable policy can also disable the toggle, so retain its explanation rather than recording any disabled control as a successful policy installation.

This key governs Desktop computer use. It does not disable Record a skill, Claude in Chrome, the built-in browser, terminal Claude Code, local MCP servers, or desktop extensions. It is not protection against someone who can modify the app or device settings. Review those paths separately, including personal-account restrictions.

Verify rollback before expanding the pilot#

An organization disable, role removal, or app-list change can take about an hour, sometimes longer, to reach Desktop. Access can continue during that interval. Record both when the administrator saved the change and when each device stopped allowing the action.

The following acceptance record is our proposed procedure, based on Anthropic's propagation and startup rules. Use a sample document and ordinary draft-only actions; do not introduce sensitive data to test a denial.

CheckEvidence to retainStop condition
Included and excluded usersAccount, role, device version, observed capability stateAn excluded user can enable computer use
Allowed and denied appsActual app ID, policy choice, restart time, observed resultA denied app remains usable or its identity is uncertain
Computer-wide disableMDM receipt, supported version, full restart, exact toggle explanationPolicy is unreadable, unreceived, or the feature remains enabled
Withdrawal during a harmless pilot taskTime the setting changed, time device behavior changed, downstream draft stateAccess still works or task effects remain unaccounted for

For an incident, use the organization's established endpoint-response procedure while policy propagates. Check the affected application and its downstream effects separately. Losing future computer access cannot recall a file already read or undo a message already sent.

Screenshots need an evidence-handling decision too. Anthropic says they are saved with the chat, and its automated action check can see the latest screenshot and retain a copy in the check record. Decide what may appear on the pilot screen and who can access retained evidence. Use the Compliance API guide to review supported exports and omissions; do not assume a chat export contains every image or downstream action.

Before adding users, retain evidence that the permitted workflow succeeded, exclusions held, and withdrawal reached each tested device. Leave a device out of the expansion if its policy receipt or shutdown result is still unknown.

Frequently asked questions

  • Do Claude's connected-folder restrictions limit computer use?

    No. Anthropic says computer use can open, change, or delete files outside connected folders through an approved app. Folder allowlists and the folder Read only setting do not apply to that path. Review the app's reachable data and use separate endpoint and application controls.

  • Does turning off computer use stop it immediately?

    An organization or role change can take about an hour, sometimes longer, to reach Claude Desktop. The computerUseEnabled=false device policy is read at startup and requires Claude Desktop 5.1231.0 or later. Verify receipt and fully quit and reopen the app; a saved setting alone does not prove containment.

  • Can MDM enable computer use without user approval?

    No. Setting computerUseEnabled to true behaves like leaving it unset. Organization access, Enterprise role access, and the user's switch still apply, and users approve apps themselves. On macOS, preparing permissions through MDM does not turn on Screen Recording or computer use.

Browse all