What DataMind Oda may do on your computer depends on three things: the access mode of the chat, the permissions on your DataMind account, and the feature switches you and your company control. This page covers those controls. For the folders Oda works in and how to change the mode, see Workspaces, files and permissions.
| Mode | What it allows |
|---|---|
| Read Only | Read files in the workspace; every change asks for approval. |
| Workspace | Write inside the workspace; anything wider asks for approval. |
| Full access | Full file access without approval prompts. Available only when your DataMind account allows it. |
Workspace is the default.
Full access is offered only when your DataMind account holds the DataMind Oda Full Access permission. Without it, the mode does not appear. If you need it, ask your administrator; Manage DataMind Oda for your company shows where they grant permissions.
Oda asks before a step that goes wider than the chat's mode allows, for example changing a file outside the workspace or running a command that needs more rights. The chat shows the request and you answer it there; see Approve or reject Oda's actions for the choices.
When a step is blocked by the mode and a wider mode would let it run, Oda can ask to retry it once with the wider mode; Command sandboxing and approvals explains how that request works.
In Auto review, a model checks each tool call before it runs. The mode carries Full access rights, so it requires an account that holds Full access. See Auto review.
Oda runs as a desktop app and as a VS Code extension, and not every feature is in both:
Settings > Developer > Advanced features shows one switch per risky feature, such as Computer use. Switches are off until you turn one on, and the first turn-on asks you to accept that feature's risks, once for your account.
Your company can also lock a switch on or off. A locked switch cannot be changed, and the reason shows beside it.
Advanced features lists what each switch does, and Computer use covers that feature itself.
Commands run under the chat's access mode: in Read Only and Workspace they stay within the mode unless you approve a wider step, and in Full access they run with your full rights. Two details of that sandbox are worth knowing:
Full access is offered only when your DataMind account holds the DataMind Oda Full Access permission. Ask your administrator to add it if you need the mode.
Yes. In Read Only and Workspace, Oda asks before a step that goes beyond the mode; in Full access, approvals are turned off and Oda acts without asking.
Auto review carries Full access rights: what it allows runs at that level, with a model checking each tool call first. For that reason it is offered only to accounts that hold Full access. See Auto review.
No. Scheduled tasks work in the desktop app only; company data (Minds), MCP servers, skills, hooks, memory and the browser work in the desktop app and in the VS Code extension. Browser tools also need the browser permission on your account.
Your company locked it: an administrator can hold a switch on or off for everyone, and the reason is shown beside the locked switch. You cannot change it on your computer; ask your administrator if you need it changed.
It stays within the chat's access mode: in Read Only and Workspace, a wider step does not run until you allow it, and only Full access runs commands without asking. In Workspace on Windows, a command also gets a private temporary folder of its own for the session; in Read Only, it gets none.