The setting lands in an admin console this week, and the first person to find it in most firms will be a staff member with a task that spans 4 apps. On November 20, 2026, computer use reached Claude Team and Enterprise plans in beta, rolling out to organizations gradually. Claude can see a user’s screen and work in the desktop apps they allow, clicking and typing the way a person would on Claude Desktop.
Direct answer: Computer use is off until an Owner or Primary Owner turns it on for the organization. On a Team plan, that 1 switch covers every user, because Team plans carry no custom roles. On an Enterprise plan, roles can limit who gets it. Set the app list and the screenshot rule before the switch, because screenshots are saved with the chat and can hold client information.
An agent that clicks through your desktop works wherever the mouse can go. The admin article on how to set up computer use for Team and Enterprise plans reads less like a launch note and more like a control list, and that is the right way to read it.
Who can turn computer use on, and who gets it?
Only an Owner or Primary Owner can change the organization setting. If the setting is missing in your console, the rollout has not reached your organization yet, or your organization cannot have it. A missing switch is a vendor timeline. It calls for a wait, and it never calls for a workaround on personal accounts.
The plan split decides the size of the first step. Team plans have no custom roles, so the setting covers every user on the plan the moment it goes on. The owner switch is the whole rollout decision, and it should get the care a whole rollout decision deserves.
Enterprise plans carry the finer tool. Computer use sits inside custom roles as a capability. Users on built-in roles get it as soon as the owner turns it on. A person on a custom role needs a role that includes the unified Chat and Cowork capability, and the owner clears every role that should stay out before the switch lands.
The feature also has a shape limit worth knowing on day 1. It works in the new Claude experience, where Chat and Cowork run as 1 surface. It does not work in tasks started with the separate Cowork option, and it does not run in Claude Code.
What should you set before the switch?
Set the app list first. The App access setting holds 2 lists, an allow list and a block list, and only an Owner or Primary Owner can change them. Start with an allow list that names the few apps in the pilot task. An empty allow list in use means Claude can use no app at all, which is a safe place to stand while you decide.
Plan around the lag. Changes to the setting, to role access and to the app lists can take about 1 hour, sometimes longer, to reach each user’s Claude Desktop. A denied app can stay usable inside that window. Turn the feature off and the same lag applies, so a Friday afternoon experiment can run into Monday before the off switch fully lands.
Write the screenshot rule next. Claude takes screenshots to see and move around the screen, and those screenshots are saved with the chat. They can include personal or confidential information that happened to sit on the screen. The automated check that reviews Claude’s actions can also see the latest screenshot.
For a Canadian firm, that record lands on your desk. Client files, health details, payroll screens and tax records all sit 1 alt-tab away from the task you assigned. A screenshot saved inside a chat is a record your firm created. Decide which screens staff close before a session, and write that list down. The review habit in Review AI-generated work with one signed line before your name goes on it extends to screen work with 1 change. The reviewer reads the record the session left behind, screenshots included, before the output goes out under a name.
What do users and computers need?
Each user needs the latest Claude Desktop, open on the computer Claude will use. Each user turns on Enable computer use there, on each computer and for each account. A laptop and a desk machine are 2 separate setups.
Use from Claude on the web or from Claude Mobile needs 1 more organization setting, Computer access, turned on, with the chat connected to the computer Claude will use. On a Mac, the work also needs the Accessibility and Screen Recording permissions granted to Claude Desktop.
Firms that manage computers with a device management tool hold a harder off switch. A policy key can keep computer use off on chosen computers, whichever account signs in. The key needs a current Claude Desktop build, and the app reads it at startup, so a quit and reopen is part of the check.
How should a Canadian team pilot it?
Pick 1 task that crosses apps and wastes real time. Data moved from a spreadsheet into a form. A report assembled from 3 screens. Give the pilot to the small group the role settings allow, on an allow list that names only the apps that task touches.
The authority lines in When an agent buys for you, set the authority before the first order hold on a desktop too. Write what the agent may open, what it may change, and what it may never touch, before the first session. The job description method in Give your AI agent an 8-line job description before access gives that writing a shape a team can finish in 1 sitting.
Judge the pilot the way Your first always-on agent looks great on day 9. Judge it on day 90 judges any agent that keeps working while you look elsewhere. Day 1 shows speed. Day 90 shows drift, odd clicks and the screenshots nobody meant to save. Read the session records each week of the pilot and count the saves your rule should have prevented.
No hands-on test ran in a live Team or Enterprise organization for this piece. The setup lines above come from the vendor’s own admin article, read in full. Your pilot is the test, and the records it leaves are the result to trust.
Recap: Computer use reached Team and Enterprise plans in beta on November 20, 2026. An owner turns it on, Team plans give it to every user at once, Enterprise roles can narrow it, and screenshots saved with each chat can hold client information. This week, write the app allow list and the screenshot rule for 1 pilot task, and keep the switch off until both sit in writing.