Permissions
Set what the agent may do without asking: writing files, running commands, using the browser and calling apps.
Feature Updated 19 Nov 2026What Permissions is
Permissions sets the most the agent may do for a member without asking: changing files, running commands, using the browser and calling apps. It also decides which chat modes members may pick. Members can always be stricter for themselves, never looser than you allow.
Where to find it
In the console, open Permissions under Policies in the sidebar. The Policy scope menu at the top switches between Whole organization and each team. Owners and admins can change it.
Set tool permissions
- Open Permissions.
- In the Policy scope menu, choose Whole organization or a team.
- Under Tool permissions, choose Auto, Ask or Off for File writes, Shell commands and Browser.
This is the most a member may allow. Members can always choose something stricter. - Optional: on the organization scope, click the lock next to a row to lock it for teams.
Teams can then be stricter, never more permissive. - Click Publish organization, or Publish with the team's name, such as Publish Sales.
What the levels mean
| Level | The agent |
|---|---|
| Auto | Acts without asking. |
| Ask | Asks the member before each action. |
| Off | Cannot do it at all. |
All three start on Ask. Reading files is always allowed and is not on the page.
Set the level for apps and integrations
The Apps and integrations row sets one level for every action of PandaOS apps and MCP servers.
| Option | Effect |
|---|---|
| Auto | Every action runs without asking |
| Ask for changes | Read-only actions run, the rest ask first |
| Ask for everything | Every action asks first |
| Off | No action runs |
The default is Ask for changes. An app marks its own read-only actions. An MCP tool counts as read-only only when its server marks it so, and any other tool asks. To set rules for single actions, see Apps and MCP.
Choose the chat modes
Members pick a mode per chat. Under Chat modes, switch off All permissions, which runs tools without asking within the tool permissions, and Auto-edit, which applies file edits without asking. Plan and Ask first are always on.
When All permissions is off, automations set to All permissions run in rules mode instead. On the organization scope, a mode you switch off can be locked for teams, and then reads Locked off. Switching off a chat mode needs a current PandaOS on members' computers, see How policies work.
Members who use Codex
Codex has no approval step per action, so PandaOS applies your levels through the way Codex runs. With File writes on Ask, every file change asks the member first. With Shell commands on Ask, Codex asks before any command it does not already know to be safe. When either one is Off, Codex works read-only and cannot change files.
Warning: Off for shell commands still lets Codex run read-only commands
On Codex, Shell commands on Off blocks every command that would change something, but commands that only read can still run.
What members see
| Setting | In the app |
|---|---|
| A level is Off | Those tools are removed. In Settings, Permissions, the row is disabled and reads "Off: your organization does not allow this". |
| A level is Ask | The approval card says "Your organization asks you to confirm" what the agent is about to do. With File writes on Ask, All permissions and Auto-edit both behave as Ask first. With another level on Ask, All permissions behaves as Auto-edit. |
| A chat mode is off | The mode leaves the picker, which reads "All permissions is disabled by your organization." Chats move to the next allowed mode. |
| All permissions is off | Automations show "Your organization disabled All permissions, so this run uses rules mode and your organization's tool permissions." |
Members get the change within about 5 minutes, and sooner when they restart PandaOS, wake their computer or click Refresh in Settings, Organization.