A permission preset is the named bundle behind a chat's access mode. It sets two things at once: how far Oda may change files, and whether steps that go wider ask you first. This page covers the presets and how they are remembered; Workspaces, files and permissions covers the workspace folder and what each mode allows in practice.
| Preset | What it does | When it asks |
|---|---|---|
| Read Only | Read files and look things up; file changes are stopped. | A wider retry asks you first. |
| Workspace Write | Changes inside the workspace folder, plus some temporary areas the system needs. | Wider steps ask you first. This is the default. |
| Full access | Anything a command can reach. | Never. Offered only while your DataMind account allows it. |
| Auto review (EXP) | Runs without the file limits, like Full access. | Never, but a model checks each tool call before it runs. |
Read Only and Workspace Write keep the approval prompts on; Full access and Auto review turn them off. When a step is blocked by the current preset, Oda can ask to retry it once with a wider one; Command sandboxing and approvals explains that request.
You can also switch by typing. A complete / command with a preset name changes the chat with no dialog, and / on its own reports the current preset and which ones are available. An unknown name changes nothing. Picking the preset the chat is already in changes nothing, and if a switch is refused the control returns to the current value. Commands in general are covered in Slash commands and references.
Settings > General > Permission sets the preset that new chats start in; the row explains itself:
New chats start in the mode you chose last, here or in a chat
To find the row, see General settings.
If the chat's current file limits and prompt settings match no offered preset, the control shows Custom, with the description Current sandbox and approval settings do not match a preset. This can happen after a preset stops being available. Choosing a preset from the menu moves the chat back onto one.
Workspace Write, until you change it. After that, a new chat starts in the mode you chose last, whether you chose it in a chat or in Settings; chats already open keep the preset they had.
Yes. A complete / command with a preset name switches the chat with no dialog, and / on its own reports the current preset and what is available. An unknown name changes nothing.
The chat's current file limits and prompt settings match no offered preset, so the control shows Custom and explains with Current sandbox and approval settings do not match a preset. Pick a preset from the menu to move the chat back onto one.
Auto review is experimental and applies to the current chat only, so it appears in the chat's menu, never as a default for new chats.
It marks Auto review as experimental. The chat runs without the file limits while a model checks each tool call before it runs; the confirmation warns that it may allow or deny a call wrongly and that it uses extra tokens.
No. A scheduled task uses the Access choice set on the task, and its runs never change the default for your chats. See Schedule recurring tasks.
It leaves the menu, and a chat that was using it falls back to Custom. In Settings, a saved default that is no longer offered is shown as the default in effect instead. When Full access stops being allowed, the chat returns to the default mode.
Turning on Full access or Auto review always asks first. The Full access dialog warns that Oda will ask you less often and that new chats will also start in Full access until you choose another mode; Enable Full access stays disabled until you tick I understand the risks and want to continue, and Cancel keeps your previous preset.