Autonomy policies
An autonomy rule is your standing answer to the question the consent decision asks on every tool call: run, ask a person, or refuse. This page shows how to write rules, how the agent level works, and how to test the result.
Who this is for: administrators who decide what an agent may do alone.
You need: Edition: Basic and above. See Editions.
Rules are managed by MitDesk administrators in Configuration ▸ Rules ▸ Autonomy Rules.
Write a rule
A rule gives one answer and names where it applies.
- Open Configuration ▸ Rules ▸ Autonomy Rules and create a rule.
- Give it a Name.
- Choose the Level: Refuse, Ask a human or Execute.
- Fill the scope. Every scope field is optional, and an empty field means "any":
- Tool: the name of the tool.
- Model: the Odoo model the call would touch.
- Operation: a method name, for example
action_confirm. - User and Group: who the rule is for.
- Save.
A rule with no scope matches everything. A rule with a tool, a model and a user matches very little. That is usually what you want.
Execute means no human click
An Execute rule lets matching calls run without anyone approving them. Keep the scope as narrow as you can. For automations, prefer a grant on a published flow. It creates and removes its own narrow rule.
The most specific rule wins
MitDesk does not read your rules from top to bottom. It counts how many scope fields each rule fills in. The rule with the most wins. Sequence only decides between rules that are equally specific. This is the Specificity number you see on the rule.
What a rule cannot do
A rule replaces the first answer from the floor. It does not replace the guardrails that come after it.
- An Execute rule on a call that must be seen by a person becomes Ask a human. This covers money, the control plane, deleting, tools that need consent, targets only known at run time, and method-shaped calls.
- An Execute rule never gives Odoo rights. The tool still runs as a real user with that user's record rules.
- Refuse is always kept.
Some writes are refused before any rule is read. See How consent works.
Check what a rule does
- The rule form shows Approval history for its tool: how many approvals in the last 30 days were approved or rejected, and whether financial actions were among them. Look at this before you widen a rule.
- Click Test this rule to open Test a decision with the tool and model filled in.
Test a decision
Configuration ▸ Rules ▸ Test a decision asks the engine what would happen, without doing it. Nothing runs and nothing is recorded.
- Choose Acting as. Only approvers and administrators can choose another person.
- Choose the Operation (the tool).
- Optionally choose On data (the model) and Through model (the AI model that would receive the data).
- Click Explain.
You get one answer: Runs without asking, Asks a person first or Refused. Below it, a table lists each step: the stage, its answer, where it is configured, and the detail. If the AI model would send the data somewhere it may not go, the answer is Refused and the table says why.
The answer is about permission only. A call that is allowed can still fail, for example if an argument is wrong or the record is gone.
The autonomy level of an agent
Every agent has a Default autonomy level. Find it on the agent form in Configuration ▸ Who does the work ▸ Agents.
| Level | What it means |
|---|---|
| Read only | The agent may look, never change. Every write is refused. |
| Proposes | Changes arrive as proposals that a person approves. This is the default for new agents. |
| Asks first | The agent asks before every change. |
| Acts alone | The agent may act alone, inside the floors and guardrails. |
The level is a ceiling, not a switch. It can only make an answer stricter. Acts alone does not unlock money, sensitive data or the control plane. Turning the level down always works at once. Turning it up changes nothing by itself, because the floor, your rules and the guardrails still decide.
Proposes and Asks first both wait for a person. The approval card shows the difference: a proposal says the assistant is volunteering the action, and a consent card says a person is required whoever asked.
A hired digital employee has its own level and a highest level it keeps even if its job role changes. The strictest level wins.
Rules that are written for you
Approve & don't ask again
On an approval card, an approver can click Approve & don't ask again. MitDesk approves this call and saves a narrow rule for the same tool, model and operation for the user who asked.
MitDesk builds the rule from the saved job, not from the request, so nobody can widen it by sending a changed request. The button is not offered when:
- Require a separate approver is on,
- the request runs as a shared service account, because the rule would then cover everyone who uses that agent,
- the call must always be seen by a person.
If the agent's level is below Acts alone, the saved rule is capped and the agent keeps asking. MitDesk tells you this when you click.
Do not ask me again
Any user can stop their own approval step for ordinary work. Open Governance ▸ Do not ask me again, add the tool, and click Stop asking me. Click Ask me again to undo it.
Rules for waivers:
- The waiver is always for you. You cannot create one for someone else.
- Money, sensitive targets, the control plane, deleting, tools that need consent, run-time targets and method-shaped calls always keep their approval. The Why it still needs approval column tells you why.
- A tool that normally goes to review must also be reversible. A tool that can assign work to yourself or to others stays refused.
A waiver creates an ordinary rule. Turning it on and off is written to the audit log.
Run-as accounts
An agent or automation can run as a dedicated account. MitDesk does not accept:
- the superuser or OdooBot,
- portal users,
- administrators,
- archived accounts,
- accounts without MitDesk user rights.
"Run as admin" would be the same as no access control, so it is not offered. Choose a normal internal user that has only the access the job needs.
If it does not work
If a run-as account is refused, see Troubleshooting.
Related
- How consent works: the four steps and the guardrails.
- Decisions: approving and answering: where approvers decide.
- Dry runs and grants: standing permission for a published automation.
- Audit and evidence: rule changes and waivers are recorded there.
- Permissions and groups: the Odoo rights that a rule never changes.