MitDesk docs
Using MitDesk

Decisions: approving and answering

4 min read Odoo 20.0

MitDesk ▸ Decisions is the one place where work waits for a person. Use it to approve or reject what an agent wants to do, and to answer questions an agent asked.

Who this is for: people who approve or reject what an agent wants to do.

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

A decision is one of two things:

  • An approval: an action is parked until a person allows it. See How consent works.
  • A question: an agent asks its user something and needs a yes or no.

Overdue Odoo activities are not decisions. You find them in My work.

Decisions: counters, tabs, and one row for each request with Approve or Answer

The Decisions screen

The top shows five counters: Need approval, Need your answer, High priority, Oldest waiting and Decided this week. They are counted with your own rights. A request that expired is not counted as decided, because nobody decided it.

Below the counters you can:

  • switch between all items, approvals and questions;
  • choose All I can see or Waiting on me (only what you can decide);
  • filter by business area, when digital employees have departments;
  • search with Search decisions…;
  • click Ask MitDesk to talk about the decisions in the chat.

Select a row to see the details on the right. Details shows what will happen and why. History shows what happened to the request.

Who sees what

There is no special group for this screen. You see what the approval rules of Odoo allow. An approver sees all approvals and the questions of their own agents. Other users see their own requests. They can also withdraw a request they made.

Approvals and questions

An approval waits for your decision.

  • Approve lets the action run.
  • Reject needs a reason. MitDesk keeps the reason on the decision, and it shows in the History as "Reason given". The audit log notes only that a reason was given. It does not copy the text.
  • The More button opens the full approval form. It has Approve and Deny.

A question is answered with Answer yes or Answer no. Only the person the agent asked can answer. An answer gives no permission. Every action the agent takes afterwards still asks for its own approval.

The approval form with the exact call, the old and new value and who may approve

Approve several at once

Click Select, tick the approvals and click Approve selected. Each approval is still approved and logged on its own. If some of them change money, MitDesk asks for one more confirmation. You can also reject the selection with one reason.

What a card shows before you decide

  • A plain title, such as "Send a payment reminder", and a sentence about what will happen.
  • The exact field changes, from the old value to the new value.
  • The record, with an amount when there is one, and a button to open it.
  • Who asked (the agent or the digital employee) and the account the action will run as.
  • Why a person is needed, and the impact: does it touch financial records, is a run paused on it?
  • Tags such as Financial, Policy, Sensitive, Irreversible, and when it expires.
  • Whether you may decide it. If not, the card names who can.

Priority is simple. A request is high if it is financial or has waited 72 hours or more. It is medium after 8 hours.

If you may not read the target record, the card says "Not visible to you". It still lists which fields will change, so you can decide.

Approvals inside the chat

An agent's request also appears as a card in the chat. You can approve or deny it there. In the chat, Approve & don't ask again is offered. It saves a narrow automatic rule from your decision. It is not offered when:

  • the item is a question;
  • the action touches financial records or is one that must always ask;
  • separation of duties is on (nobody may approve their own request, so a rule decided in advance would skip the second person);
  • the request runs as a shared service account. The rule would then apply to everyone who uses that agent.

If separation of duties is on, you cannot approve your own request, but you can always reject it.

A changed target stops the action

Approving does not run the action at once. It releases the parked run, which starts a moment later. In that time the record could change.

So MitDesk compares the target again when the run starts. For tools that name a model and record ids, it checks the tool, the model, the ids, the values or method arguments, and the last-change time of each record. If anything is different, the action does not run on the changed target.

  • A financial action fails and is not tried again.
  • Other actions go back to you for a new approval. The card shows the current values.

Expiry

A request that waits too long expires. The run behind it fails, and an activity is created for the approvers shortly before. An expired request can never be approved.

The decision history with past decisions and their state

Oversight ▸ Approvals shows all requests as a list, and Oversight ▸ How Approvals Work explains the three outcomes of a request.

If it does not work

If a task stopped after some approvals, or a run-as account is refused, see Troubleshooting.