MitDesk docs
Getting started

What MitDesk is

3 min read Odoo 20.0

MitDesk is an AI assistant inside Odoo. You ask a question, and the answer comes with the records it used. If the assistant wants to change something, it follows the same access rules as you.

Who this is for: anyone who wants to know what MitDesk is.

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

A chat answer with a list of sources under it and a panel on the right that says what this agent may do

MitDesk reads and writes through Odoo itself, as the user who asked. It keeps no second copy of your Odoo data. What the model needs for an answer is sent to the model provider you chose.

What it does for you

How it stays safe

Three things work together.

One entry point

The assistant can reach Odoo only through one internal gate. Two functions, request() and run_tool(), are marked private. The browser cannot call them. This matters because the gate is told which user is acting. If a browser could set that value, any user could pretend to be a colleague.

The gate runs each tool as the acting user. If that would mean running as the Odoo superuser, MitDesk refuses. An unknown or archived user is also refused. Run Odoo without the -O option and without PYTHONOPTIMIZE. This is the normal way to run Odoo, and the safety check depends on it.

One decision for every action

Each tool call ends in one of three ways: it runs, it waits for a person, or it is refused. If MitDesk cannot decide, it asks a person. Read more in How consent works.

Some actions always wait for a person, whatever the rules say. These include financial or sensitive records, changes to the rules and agents themselves, destructive tools, and any call whose target is not known beforehand. The agent's autonomy setting can only make things stricter. It never lifts these limits.

The "How approvals work" guide: an action runs, waits for a person, or is refused

One record of what happened

Each tool call that runs, or fails while running, adds a row to the audit log. The row names the user, the tool and the kind of data. A call that is refused is written to the audit log too, with the reason.

The audit log: time, who, what happened, which tool, whether money was involved, and the data class

In the base module, no user group may change or delete audit rows. This rests on access rules alone. Code that runs as superuser could still change them. The Compliance module (Business) closes this gap and adds a hash chain. A hash chain is a series of checksums, each built from the one before. If someone changes or removes an old row, the chain no longer matches. See Compliance support.

What it is not

  • It does not act on its own by default. The agent that comes with MitDesk is set to Read only. A new agent starts at Proposes, where each change waits for a person to approve it.
  • It has no account of its own. A chat runs as the person who typed. An agent can be set to run as a chosen user instead. See Permissions and groups.
  • It does not give anyone more access. If your account cannot read a record, the assistant cannot show it to you.
  • It is not a compliance certificate. MitDesk gives you switches and evidence. Whether your setup is lawful depends on the providers you use and the settings you choose.

The agents list: model, response style and default autonomy for each agent

Next steps