MitDesk docs
Getting started

Permissions and groups

5 min read Odoo 20.0

This page explains who can do what in MitDesk. It covers the three MitDesk groups, what each one sees, and the one case where an agent runs as someone else.

Who this is for: administrators who give people access.

You need: Edition: the groups are part of the core module, so they apply to every edition. See Editions. Some other modules add their own menus and groups. Those are described on the pages of those modules.

The main rule

The assistant runs as the person who asks. It can never see or change more than that person could.

MitDesk does this in code, not only by policy. Before a tool runs, MitDesk switches to the acting user. It refuses to run as the Odoo superuser. If the user is unknown or archived, it stops. The assistant reads and writes through Odoo, so Odoo's access rights and record rules apply as if the person had clicked through the screens.

The private functions request() and run_tool() do this check. The browser cannot call them. Run Odoo without -O or PYTHONOPTIMIZE, because the check depends on that.

The three groups

MitDesk adds three groups. Each one includes the one before it.

Group Includes What the person can do
MitDesk User Odoo internal user Use the chat. Read their own chats, messages, jobs and audit rows. Read agents, AI models, endpoints, tools and skills, but not change them. See their own approval requests. Open Oversight, where they can follow their own requests.
MitDesk Approver MitDesk User Everything a User can do, and read and answer approvals of the kind "classifier gate", plus their own requests. Cannot create or delete approvals. Sees the Governance menu, where each person manages their own Do not ask me again rules.
MitDesk Administrator MitDesk Approver Create, change and delete agents, AI models, endpoints, tools, autonomy rules and conversations in their own companies. Sees the Configuration menu. Can test provider connections and change autonomy rules. Reads the whole audit log of their companies.

A user with Odoo's Settings access becomes a MitDesk Approver, not an Administrator. Being able to set up Odoo does not mean deciding what the AI may do. Odoo Settings users can edit and import skills, because skills are changed with that right.

The Approvals list: requested, decision, level, asked by, expires and state

What each group sees in the menu

Menu Who sees it
Cockpit, Chat, Decisions MitDesk User
Oversight (Approvals, Audit, How Approvals Work) MitDesk User
Governance (including Do not ask me again) MitDesk Approver
Configuration (Settings, Engine, Agents, Rules, Jobs, Conversations) MitDesk Administrator
Configuration ▸ Who does the work ▸ Skills MitDesk Administrator who also has the Odoo Settings right

Some Governance entries need an extra module, for example Compliance or Sovereign. Some entries, such as Reported answers, are only for Administrators.

The audit log cannot be changed

No MitDesk group may write, create or delete audit rows, not even an Administrator. With the Compliance module installed, the model also refuses changes from privileged code. See Audit and evidence.

Record rules

Users see only their own chats, messages, attachments, jobs, audit rows and cockpit state. Administrators see all of them in their companies.

On top of this, there are company rules that apply to everyone, with no group. This is on purpose. A rule that belongs to a group is combined with other group rules, so an "admin sees all" rule would let the administrator of one company read another company. A rule without a group is always applied together with the others, so nobody can bypass it.

One kind of record has no administrator exception: the rules a user creates for themselves with Do not ask me again. Each user manages only their own. Another person must not be able to grant permission on your behalf.

Reported answers are visible to the person who reported them and to the owner of the chat, because the report contains the whole chat. Administrators can see all of them in their companies so they can review reports.

Agents that run as someone else

An agent can have a Run as User. Then its tools run as that account, not as the person who talks to it. This is the only exception to "runs as you", and it has limits on both sides.

Who the agent may run as. Not the superuser or OdooBot, not a portal user, not an Odoo administrator, not an archived account, and only an account that already has MitDesk User rights. Running as an administrator would remove all access control, so MitDesk refuses it. A digital employee's own agent may not have its own Run as User. Every MitDesk user in the company can open such an agent, and a run-as account would let all of them act as that account.

Who may open it. An agent with a run-as account can be opened in chat only by the users and groups named in Available to. If you name nobody, nobody can open it in chat. It can still run without a person, for example from an automation or a schedule.

The chat shows this clearly. The header says "runs as" and the name. The side panel says that this user's access rules apply.

The agent form for MitDesk Assistant: model, response style, default autonomy, run as user, and tabs for Prompt, Tools, Sources, Skills, Limits and Memory

Require a separate approver

In MitDesk ▸ Configuration ▸ Settings, the block Consent & approvals has the switch Require a separate approver.

  • Off (default): an approver may approve their own request. This suits a company with one person in charge.
  • On: every request waits for a different person. The person who asked can never approve it.

This setting does not decide which requests need approval. That is the job of the consent engine.

Tools for an agent

An agent that has no explicit tool list does not get all tools. The tool call_method, which can call almost any method on any model, is not included. Its effect is too wide to describe in advance. An administrator can still add it by name.

AI Tools grouped by area, with the number of tools in each

Next steps