When Oda is denied access

When a command or a file change tries to make a change the chat's access mode does not allow, the file sandbox stops it, and DataMind Oda can ask you to allow one wider retry. This page is the reference for that moment: the notice a denial leaves behind, the retry and its approval, and what Oda does when it cannot limit writes to a folder. For the walkthrough with the approval card, see Command sandboxing and approvals.

What a denial looks like

When the file sandbox stops a change, the result carries the denial notice:

• The notice reads [sandbox: file access denied under <mode> mode], where <mode> names the mode the action ran under, for example [sandbox: file access denied under read-only mode].
• The denied change is not made. A denial is the limits working as intended, reported as its own outcome, separate from how the action ended.
• Oda reports the denial instead of retrying quietly. The result adds that the exact same action can be retried once with a wider mode, and that the approval prompt asks you first.

The wider retry and its approval

A wider retry exists only after a denial, and it repeats the exact same action once. Nothing runs before your answer.

• Oda asks for the narrowest wider mode that can work, with a one-sentence reason.
• The ladder is closed. A retry can only widen:

• A request that repeats the mode the action ran under needs no approval, and a request for a narrower mode is refused before it reaches you.
• The approval prompt states the request in the form escalate sandbox to <mode>: <justification>, naming the mode Oda wants to widen to and the one-sentence reason.

The answer decides that one action:

• Allow once: exactly that one action runs at the wider mode. The widening covers that call only; the chat keeps its access mode, and a later action that goes wider asks again.
• Reject: the action does not run, and the rejection is final for that attempt. Instructions you add with the rejection are passed on, and Oda can follow them instead.
• If the request is cancelled, or nothing can ask you, the action does not run: a retry never proceeds without your answer, and when no approval prompt can be shown (for example in a scheduled run) the request is refused instead. See Schedule recurring tasks.

The request works like Oda's other approval cards; Your first task lists the choices.

When Oda cannot limit writes to a folder

When the file limits cannot be applied to the folder, Oda does not drop the limits quietly. It names the folder and the reason, for example:

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.

When the system refused the change the limits need, the message reads:

DataMind Oda can't limit writes to <folder> because Windows denied changing its permissions. Choose a folder you own, or switch to Full access.

When a prompt can reach you, Oda asks before running that one action without restrictions:

DataMind Oda can't limit writes to <folder>. Run this <subject> without restrictions?

Here <subject> is command for a shell command and operation for a file change. The answer decides that one action:

• Allow once: exactly that one action runs without restrictions, as it would in Full access; nothing else changes, and the chat keeps its access mode.
• Reject: the action does not run: Running this <subject> without restrictions was not approved, so it did not run. You can allow it when Oda retries the action, switch the chat to Full access where your account offers it, or use a folder you own.
• When nothing can ask you, the action also does not run: No approval prompt is available here, so this <subject> did not run. A cancelled request ends the same way, without a run.

Questions, answered

What does the denial notice in a result mean?

The action tried to change a file the chat's mode does not allow, and the file sandbox stopped that change. The notice names the mode the action ran under, the denied change was not made, and the result adds that the exact same action can be retried once with wider access. A denial is not a failure of the action: it is the limits working as intended.

How far can a retry widen?

Only wider, and only as far as it needs: from Read Only it can widen to Workspace Write or Full access; from Workspace Write, to Full access only. The ladder is closed, and Oda asks for the narrowest wider mode that can work.

Why was a request for wider access refused before it reached me?

A request must name a strictly wider mode on the ladder and carry a one-sentence reason; a request for a narrower mode, or one without a reason, is refused before it reaches you. When nothing can ask you, the request is refused as well, and the action does not run.

What happens if I reject a wider retry?

The action does not run, and the rejection is final for that attempt. Instructions you add with the rejection are passed on, and Oda can follow them instead of the retry.

Does allowing a wider retry change the chat's access mode?

No. The widening covers that one action only. The chat keeps its access mode, and the next action that goes wider asks you again.

How many times can the same action be retried?

Once: after a denial, the exact same action can be retried a single time with a wider mode. If you reject it, cancel it, or nothing can ask you, that attempt ends, and Oda continues with the task another way.

Why can't Oda limit writes to my folder?

On some computers the limits cannot be applied to a folder, for example when the system refuses the permission change they need, or when nothing on the computer can apply them. Oda does not drop the limits quietly: it says what went wrong, and asks before running that one action without restrictions. Choosing a folder you own avoids the situation.

What happens if I decline the run without restrictions?

The action does not run: Running this <subject> without restrictions was not approved, so it did not run. You can allow it when Oda retries the action, switch the chat to Full access where your account offers it, or use a folder you own. When nothing can ask you, or the request is cancelled, the action does not run either.

Can I avoid the folder problem in future?

Yes. Use a folder you own for the workspace, or switch the chat to Full access where your account offers it; Workspaces, files and permissions covers the modes, and Permissions, approvals and feature controls covers what your account offers.