Modes without confirmation
Decide per role who may choose the modes "Accept edits" and "Auto" in Cowork and Code and have connections approved automatically
In Cowork and Code, members pick a mode that decides how much the assistant may do without asking. With the permission Work without confirmation in Cowork and Code you decide per role who may use the modes in which the app no longer asks before every change. You find it in the permission editor under Organization settings → Members & access → Roles in the section Apps & extensions, right next to Use Code in the desktop app.
As with every permission, all of a member's roles count: if any of their roles grants it, the member has it. The Admin role always has it.
What is missing without the permission
If a member does not have the permission, the desktop app hides the modes Accept edits and Auto in Cowork and in Code. The switch Approve connections automatically is gone as well. Actions of connected services such as integrations and MCP servers keep asking one by one.
A member without the permission is still not asked at every step. Whatever an allow rule or an earlier approval covers runs without asking even without the permission, and approval cards still offer Always allow.
The member can still choose Normal and Plan mode, and also Don't ask. That mode is the strictest one: the assistant only runs what a saved approval or a rule already covers and declines everything else without asking. Scheduled tasks need it, which is why it stays allowed.
If a member had a blocked mode selected, the app switches to Normal. When a plan is approved and when you switch with Cmd/Ctrl+Shift+M, it only offers the modes the member may use.
Which roles have it
Roles that already existed before this permission was added have it. Nothing changes for your members until you take it away from a role. A custom role you create from now on only has it once you switch it on.
If, say, only employees who have been briefed should work without confirmation, switch the permission off in the User role and give it to a custom role that only those people have.
What the server enforces and what the app decides
Without the permission, the server always creates an approval card for actions of connected services that need an approval and refuses the review model that judges risky steps in Auto. The card is answered in the desktop app, and only when the member clicks. This also holds for older versions of the app from 0.16 on that still offer Auto and the switch: they no longer approve such cards themselves but show them with a note that your organisation requires a confirmation. These cards do not offer Always allow.
Whether a file change or a command on the member's computer runs without asking is decided by the desktop app instead. An older version that does not know this permission yet still allows Accept edits and Auto for these steps. For the setting to take effect here too, your members should use the current version. The same holds for the allow and ask rules of the agent permissions, because only the app can show an approval card. Anything that must never run belongs there as a deny rule. The server enforces deny rules as well.
Together with the agent permissions
The two settings complement each other. The permission in a role decides which modes a member can choose. The agent permissions under Tool policies apply to every member in every mode: a deny rule always applies, and an ask rule forces the approval card even where a member may work without confirmation.