DataMind Oda runs commands on your computer as it works, for example to prepare a report or tidy a folder. Every command runs inside the limits of the chat's access mode. When a command tries to change files the mode does not allow, the file sandbox stops it, and Oda can ask you to allow one wider retry.
The chat's access mode decides what commands may change on your computer.
| Mode | What a command may change |
|---|---|
| Read Only | Nothing. A command that would change files is blocked. |
| Workspace Write | Files under the workspace folder, plus some temporary areas the system needs. This is the default. |
| Full access | Anything the command can reach. No limits are applied. |
Reading is not limited by these modes. To change the mode, use / or the mode button in the message box; see Workspaces, files and permissions.
When a command tries to change files outside the limits, the file sandbox stops that change:
Operation not permitted on macOS or Read-only file system on Linux.Oda may then ask to retry the same command once with wider access, or continue with another approach.
After a blocked command, Oda can ask to run the same command once more with wider access. What a retry can widen:
| From | A retry can widen to |
|---|---|
| Read Only | Workspace Write or Full access |
| Workspace Write | Full access only |
The request works like the other approval cards in Oda; Your first task shows the choices and what each one does.
If you reject the wider access, the command does not run and Oda continues with your task in another way. It tells you the options: allow it when you ask again, switch the chat to Full access if your account offers it, or point Oda at a folder you own. If you reject with instructions, your instructions reach Oda, and it can follow them instead.
On some computers, the file limits cannot be applied to a folder, for example when the system refuses to change the folder's permissions. Oda does not run the command with the limits quietly dropped. It names the folder and the reason:
DataMind Oda can't limit writes to <folder> because no sandbox is usable on this computer.Choose a folder you own, or switch to Full access.
Before running the command without limits, it asks:
DataMind Oda can't limit writes to <folder>.Run this command without restrictions?
It tried to change files outside the chat's limits, and the file sandbox stopped it. Allow the wider retry Oda asks for, change the access mode, or point Oda at a folder that suits the work.
No. The denied change is not made. Parts of the command that ran before the denial may have completed, so check anything Oda reports it changed.
One retry of the same command, with the narrowest wider access that can work. Nothing runs before you answer, and the widening applies to that one step only.
No. Wider access always needs your answer first. If nothing can ask you, the step does not run and Oda says so.
The command does not run, and Oda continues with the task in another way. You can allow it when you ask again, switch the chat to Full access if your account offers it, or use a folder you own. Instructions you give with the rejection reach Oda.
No. The chat keeps its mode; only that one step ran wider, and the next command that needs wider access asks again.
Pick the mode that matches the work: Workspace Write for changes inside the workspace, Read Only for look-only tasks. If the files are elsewhere, add that folder as the workspace. Full access removes the limits, but your DataMind OS account must offer it; see Permissions, approvals and feature controls.
On some computers the file limits cannot be applied to a folder, for example when the system refuses to change its permissions. Oda then asks to run the command without restrictions, and does not run it if you do not allow that. Choosing a folder you own avoids the situation.
No one is watching a scheduled run, so a request that needs your answer is not approved there. The run records that the command needed approval and continues without the wider access.