PARAS MADAN
All writing

Latest in AI

Claude Computer Use for Team and Enterprise: How to Run a Narrow Pilot

Check beta eligibility, separate desktop control from remote access, and verify app permissions before piloting Claude computer use at work.

If a teammate asks Claude to format a spreadsheet, there is a meaningful difference between giving it a copy of the file and letting it work in the spreadsheet app. With computer use, the app gives Claude a view of the screen and a way to click and type. That makes more tasks possible, but it also changes what you need to check before turning it on.

The November 20 Claude release notes announce a gradual computer-use beta rollout for Team and Enterprise. I would start with one approved app, sample data and an observable outcome rather than asking an agent to reproduce a whole employee workflow.

Check whether your organization is eligible

Anthropic's admin setup guide says the beta starts off and requires the unified Chat and Cowork experience. It supports Claude Desktop on Windows and macOS 14 or newer. The separate Cowork option and Claude Code are not supported for these plans.

The setup guide lists exclusions including HIPAA-ready configuration, Claude Code Zero Data Retention, customer-managed encryption keys, and FERPA or K-12 settings. If the switch is missing, check rollout and eligibility before asking users to troubleshoot their machines.

For an initial pilot, confirm that the admin sees the control and that the test account can start a chat in the unified experience. Do not rely on a consumer walkthrough that starts from a different mode.

Treat Computer use and Computer access as separate decisions

An Owner or Primary Owner manages Computer use under Organization settings → Capabilities → Claude Desktop. On Team, the setting covers everyone. Enterprise can use custom roles to scope it; review existing built-in and all-capabilities roles before enabling it because they may already qualify.

The separate Computer access setting matters when someone starts from the web or mobile and wants to use a linked computer. Anthropic covers that distinction in its Team organization settings guide. That route requires Computer access to be on, the chat connected to the target machine, and Claude Desktop open there.

I would start from Desktop. Remote initiation is another workflow to review later, not a prerequisite to see whether Claude can help with one local application. If a Team-wide setting is broader than you are willing to allow, keep it off rather than mistaking your volunteer pilot group for an enforced access limit.

Limit apps and keep the user's approval in the loop

The admin setup guide documents an App access setting with an allow-list option, Allow only these apps. An allowed app still needs user approval. Ask pilot members to run the latest Claude Desktop and check the permission prompts on their actual devices.

The user guide explains that initial approval is per app and can last for the session. It is not a fresh question for every click. On a Mac, check the required Accessibility and Screen & System Audio Recording permissions before the pilot, and use the organization's approved setup route.

For a spreadsheet task, approve only the app you expect to use. Keep sending, sharing, or modifying the original outside the test, and stop if Claude tries to open a second app.

Check what the app list does not protect

The organization setup guide warns that computer use is not sandboxed from approved apps, that connected-folder restrictions do not carry over, and that screenshots are saved with the chat. An app allow list does not govern every Claude tool or every page inside an approved browser.

That means “the spreadsheet app is allowed” is not the same instruction as “only this spreadsheet can be opened.” Close unrelated windows and use only synthetic sample content. If the task can be done with a copy of the document instead, use the less expansive route.

Make the first task easy to check and stop

A useful first request would be: “Read this synthetic spreadsheet, identify rows missing an owner, and report their row numbers here. Do not edit, send or share anything.” Give the tester a known answer beforehand so they can check it independently.

Run a second case where the file is missing. Check whether Claude reports that problem instead of opening a different file. Ask an excluded Enterprise test account to check that the feature is unavailable, and verify the approved app list on the pilot device.

Plan how to stop current work and how to withdraw access afterward. Anthropic says admin changes can take an hour or longer to reach Desktop, so don't treat the switch as an instant stop button. End the pilot knowing which users had access, what data was visible and whether the result was worth expanding the scope.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help AI teams explain new capabilities and rollout decisions through clear technical writing and practical storytelling.

Book a 30-minute call.