MitDesk docs
Editions and scenarios

Pro — a team can work with it

1 min read Odoo 20.0

Who this is for: teams that use knowledge, dashboards and automations.

You need: Edition: Pro, which includes Basic. See Editions.

Pro adds knowledge, dashboards and automations to Basic. It also adds the bridges to six Odoo apps that nearly every company runs: Invoicing, Sales, CRM, Purchase, Inventory and Project. A bridge gives the assistant tools made for that app, so answers come from the right records and actions are the ones the app allows.

1. Ask about your business, not just your records

With the Invoicing bridge, a question about money is answered from invoices, in your currency, with every invoice linked as a source.

The Data Analyst lists the three largest overdue customer invoices with amounts in euros, days overdue and the invoices as sources

With the CRM and Sales bridges, the Sales Coach ranks customers and explains why. It is set to Asks first: anything it wants to change waits for you.

The Sales Coach ranks three customers to focus on this week and offers to draft the next step

2. Give it knowledge

Configuration ▸ Engine ▸ Knowledge lists what MitDesk indexes for search: Odoo models such as contacts, activities and messages. Answers then cite those records. Each source shows when it was last indexed and with which embedding backend.

Knowledge sources: Activity, Contact and MitDesk Message, each an Odoo model with index state and retrieval backend

3. Dashboards

Dashboards starts from a question or a template. Describe a dashboard builds one from a sentence; every board can be private or shared with a team.

Dashboards: start from a question, and seven dashboards such as Customer & sales overview, Finance snapshot and Digital workforce

An open dashboard filters by period, compares with the previous one, and can be changed by asking the AI.

Customer & sales overview: counters and charts, period filters, "Ask AI to change this board" and Add widget

4. Automations

Automations lists every flow with its trigger and state. Create with AI drafts a flow from a description.

Automations: twelve flows with model, trigger type, state and the user they run as

The visual builder shows a flow as steps: a trigger, logic, actions. Steps that change data and need consent are marked. Dry run shows what would happen without doing it; Publish turns the flow on. A flow always runs as a named user, with that user's rights — never as superuser.

The visual builder: Every week, Company account, Log AR review note marked "consent"; the step palette; Dry run, Run history and Publish; flow settings with Runs as

Configuration ▸ What has run ▸ Flow Runs shows each run, the record it touched and whether it finished or waits for approval.

Flow runs: four runs, three done and one waiting for approval

Previous: Basic · Next: Business — everything it does.