MitDesk docs
Governing it

How consent works

5 min read Odoo 20.0

Before the AI changes anything in Odoo, MitDesk decides whether the action may run. This page explains that decision, so you can predict it and fix it when it is not what you want.

Who this is for: administrators and approvers.

You need: Edition: Basic and above. See Editions.

The three answers

Every tool call gets one of three answers:

Answer What happens
Runs The action happens at once, as the user who asked, with that user's own Odoo rights. It is still logged.
Waits for a person Nothing happens until someone approves. The request appears as an approval card.
Refused The action does not happen and no approval is offered.

Two other messages are not answers. One says that the check itself could not run. The other says that the request used up its question budget. Both stop the call and change nothing.

You can read this guide inside the product at Oversight ▸ How Approvals Work.

The How approvals work guide: what runs, what waits for a person, what is refused, and who may approve

How MitDesk reaches an answer

MitDesk works through four steps, always in the same order. It records each step, so a refusal can be explained later.

  1. The floor. MitDesk looks at the tool and at the Odoo model the call would touch. A tool that only reads, and can be repeated safely, on a normal model, runs. A tool that deletes, or that always asks for consent, waits for a person. A tool whose target is only known while it runs is refused.
  2. Your rule. The most specific matching autonomy rule replaces the floor. A rule can make things easier or stricter.
  3. The guardrails. Some calls must be seen by a person, whatever the floor and your rules say. See the next section.
  4. The autonomy level of the agent. Each agent has a ceiling. A digital employee has its own ceiling as well. The strictest one wins.

Only step 2 can loosen the answer. Steps 3 and 4 can only tighten it. A rule can never turn a refusal into "runs". The most it can do is turn it into "waits for a person".

Reading data that is also marked as "bulk data out" waits for a person, even though it only reads.

Guardrails that no rule can lift

A call always waits for a person when any of these is true:

  • It touches money, or a model that an administrator marked as sensitive.
  • It would change the records that control the AI itself (see below).
  • The tool says it always needs explicit consent.
  • The tool deletes something.
  • The target is only known while the call runs.
  • The call is "method-shaped". It calls a named method, so nothing can check in advance what it does.

The same answer applies in every place the AI works: chat, agents, automations, digital employees on a schedule, and external AI tools.

The approvals list: each row shows the level, who asked, whether it is financial and when it expires

Money

These changes always count as financial:

  • any change to a journal entry, a journal item or a payment.

Three more models are sensitive only for specific steps:

  • confirming or cancelling a sales order,
  • validating a stock transfer,
  • confirming a purchase order.

You can edit a draft sales order without a question. Confirming it needs approval.

An administrator can add more models. Open the model in Settings ▸ Technical ▸ Models (developer mode) and turn on MitDesk AI Sensitive. This switch only adds models. It cannot remove a model from the list, and it does not change the financial models.

The control plane

MitDesk never lets the AI change its own rules without a person. This covers:

  • autonomy rules and automation grants,
  • agents, skills and tools,
  • digital employees and job roles,
  • approvals and the audit log,
  • the job queue,
  • automations, with their steps and links,
  • Odoo's own access tables: groups, access rights, record rules, scheduled actions and server actions.

Reading these is normal work. Listing agents or reading the audit log does not ask anything. Only a call that could change them waits.

Some writes are refused

The generic tools that create, write, delete or call a method on any record have an extra fixed rule. They refuse certain targets outright. Examples are accounting and payment models, HR models, and fields such as bank account numbers, IBAN, amounts, journals and VAT numbers. A refusal is not a question, so there is no approval card for it.

The question budget

One request may interrupt a person only a few times. By default the limit is three questions per request. The system parameter minddesk.max_gate_questions_per_run changes it. The value 0 means no limit.

When the limit is reached, the run ends. MitDesk tells you how many approvals were requested, that anything you already approved has run, and that nothing was decided for you. Send the rest of the work as a new message to continue.

When the check cannot run

"Consent could not be checked" is not the same as "no". Nothing changes in both cases. But MitDesk tells you that this is not a refusal and that you can try again in a moment. If it keeps happening, ask an administrator to check the consent rules.

  • It does not give access. The tool runs as a real user with that user's Odoo rights. MitDesk never runs a tool as the superuser. Record rules still apply.
  • It does not read your conversation. The answer comes from the tool and the target, not from the words you used.
  • An approval fits one target. MitDesk remembers what the target looked like when the card was made. If the record changes before the action runs, MitDesk asks again. It asks at most twice more. After that, the action fails.
  • A request expires. If nobody decides, an approval closes after 24 hours.

Who may approve

  • Normally, the person who asked can approve their own ordinary change.
  • These always go to an Approver: anything that moves money, anything that changes MitDesk's own settings or permissions, a tool that picks its own target, and any action that runs as a different account.
  • Administrators can turn on Require a separate approver in the settings (block Consent & approvals). Then nobody approves their own request. Every card waits for someone else.

An approval card with Approve and Deny, the exact call, who asked and a preview of the record

If it does not work

If a task stopped after some approvals, see Troubleshooting.