MitDesk docs
Reference

Domain bridges

6 min read Odoo 20.0

A domain bridge connects one Odoo app to MitDesk. It adds a fixed set of named tools, a card on the 360 board in most cases, and sometimes a job role. Ten bridges exist. Each section below names the edition, the Odoo app it needs, and what its tools can do.

A bridge gives no extra rights. Every tool runs as the person who asks, through the same path as chat, flows and the MCP server. If you cannot read a sales order in Odoo, you cannot read it through the Sales bridge. See Modules for dependencies.

BridgeOdoo app it needsEdition
AccountingAccountingInvoicing / AccountingPro and above
SalesSalesSalesPro and above
CRMCRMCRMPro and above
PurchasePurchasePurchasePro and above
InventoryInventoryInventoryPro and above
ProjectProjectProjectPro and above
HelpdeskHelpdeskHelpdesk (Enterprise)Business and above
HRHREmployees, Time OffBusiness and above
TelephonyTelephonyVoIP (Enterprise)Business and above
MailMailDeskBusiness and above

The 360 board for one customer, with a card for each installed bridge

What always asks a person

Consent is not decided per bridge. One rule decides whether a person must see a call first. An autonomy rule can make it stricter. Nothing can make it looser. Three groups are fixed in the code:

  • Money. Any change to account.move, account.move.line or account.payment.
  • Four state changes. Confirm or cancel a sales order, validate a stock transfer, confirm a purchase order.
  • The rules about the AI. Writes to autonomy rules, agents, skills, tools, approvals, the audit log, jobs and flows, and to Odoo groups, access rights, record rules and server actions. Reading them is normal.

Every write tool in the bridges below also declares that it needs consent. In the tables, Asks means a person must approve it.

Accounting

Edition: Pro and above. Needs: Invoicing / Accounting (account). Details: MitDesk — Accounting.

The Data Analyst lists the three largest overdue invoices, with the invoices as sources

A new vendor bill from Gemini Furniture waits as a draft for review

Tool Type What it does
account_move_search Reads Searches invoices and journal entries.
account_move_post Asks Posts draft entries.
account_move_send_reminder Asks Emails the next German payment reminder for one overdue customer invoice.
account_create_vendor_bill_draft Asks Creates one draft vendor bill from an attached PDF.
account_register_payment Asks Registers a payment on one posted, unpaid customer invoice.

The reminder follows four steps: Zahlungserinnerung, 1. Mahnung, 2. Mahnung, Letzte Mahnung. The invoice must be posted, unpaid and overdue, and the customer needs an email address. Approvals keep a snapshot of the invoice. If the invoice changed after you approved, the reminder is not sent and MitDesk does not try again. Job roles: AP Clerk, AR Clerk. Board cards: Invoices / AR, Analytics / KPIs.

Sales

Edition: Pro and above. Needs: Sales (sale_management). Details: MitDesk — Sales.

The Sales Coach ranks three customers to focus on this week

Tool Type What it does
sale_order_search, sale_orders_to_invoice, sale_order_counts_by_invoice_status Reads Search orders, list confirmed orders that wait for an invoice, count orders by invoicing status.
sale_order_confirm, sale_order_cancel Asks Confirm or cancel quotations and orders.
sale_order_send_followup Asks Emails a follow-up with the quotation PDF to the customer. One open quotation at a time.
sale_order_create_invoice Asks Creates draft invoices. Nothing is posted.

Job role: Quote Chaser. Board card: Orders / Sales.

CRM

Edition: Pro and above. Needs: CRM (crm). Details: MitDesk — CRM.

The Data Analyst finds the one opportunity that has gone quiet

The tools crm_lead_search, crm_my_open_opportunities and crm_lead_counts_by_stage read. crm_lead_set_stage asks, and moves a lead to a stage of its own sales team, named by id or exact name. Job role: Lead Triage Officer. Board card: CRM / Deals, which marks a deal idle after 14 days.

Purchase

Edition: Pro and above. Needs: Purchase (purchase). Details: MitDesk — Purchase.

The Procurement Coordinator job role that the Purchase bridge ships

The tools purchase_order_search, purchase_orders_to_confirm, purchase_order_counts_by_state and purchase_order_match_for_bill read. The last one compares a vendor bill proposal with purchase orders you can see. purchase_order_confirm asks. Job role: Procurement Coordinator. Board card: Purchase.

Inventory

Edition: Pro and above. Needs: Inventory (stock). Details: MitDesk — Inventory.

The Transfer Dispatcher job role that the Inventory bridge ships

The tools stock_picking_search, stock_pending_transfers, stock_transfer_counts_by_type and stock_products_below_reorder read. The last one lists replenishment alerts and creates no order. stock_picking_validate and stock_picking_assign (reserve stock) ask. Job role: Transfer Dispatcher. Board card: Inventory / Purchase.

Project

Edition: Pro and above. Needs: Project (project). Details: MitDesk — Project.

A Delivery PM employee waits for a decision on a project activity

The tools project_task_search, project_my_open_tasks and project_task_counts_by_stage read. project_task_set_stage asks, and moves a task to a stage of its own project. Job role: Delivery PM. Board card: Projects.

Helpdesk

Edition: Business. Needs: Helpdesk (helpdesk), which is part of Odoo Enterprise. Details: MitDesk — Helpdesk.

The Ops Assistant classifies two new tickets on its own, under the auto rules

helpdesk_ticket_search reads. These ask: helpdesk_ticket_classify (adds tags, and creates a tag that does not exist), helpdesk_ticket_set_priority, helpdesk_ticket_assign, helpdesk_draft_reply and helpdesk_link_kb_article. A draft reply is an internal note. It is never sent to the customer. Job role: Support Triage. Board card: Tickets.

HR

Edition: Business. Needs: Employees (hr) and Time Off (hr_holidays). Details: MitDesk — HR.

Approving time off is refused: leave records are protected, and the answer says where to approve it yourself

Three read tools, all about you or your team: my_leave_balance, my_onboarding_progress and team_absences_today (your direct reports). There is no HR write tool, no job role and no board card. When you install it, the bridge marks the employee, leave, contract and payslip models as sensitive, and adds ten HR and payroll models to the cloud deny list.

Telephony

Edition: Business. Needs: VoIP (voip), which is part of Odoo Enterprise. Details: MitDesk — Telephony.

The 360 board of one customer, with the Telephony / Calls card

The tools voip_call_search, voip_recent_calls, voip_missed_calls, voip_call_detail and voip_call_kpis read. voip_call_generate_enrichment asks, and writes a summary, action items and sentiment for one finished call. It uses the notes and activities already on the call. MitDesk does not record or transcribe calls, and leaves the caller's name and number out of what the model sees. You choose the model in Settings under Call enrichment model. Board card: Telephony / Calls.

Mail

Edition: Business. Needs: MailDesk (maildesk_mail_client). Linking mail to records needs MailDesk Pro. Details: MitDesk — Mail.

Cockpit business areas, with a MailDesk card next to the other apps

This bridge has 36 tools: reading mail and threads, contacts, attachments as text, links between mail and records, tags, flags, moves, drafts, mailbox health and automation rules. It cannot send or delete mail. Reading is free. Changes ask first by default, and record links, tag creation, draft deletion and rule changes always ask. Mail is treated as untrusted text. Board card: Mail.

Job roles come with Digital Employees

No bridge depends on minddesk_workforce. A bridge loads its job roles only when Digital Employees is installed. The ceiling of each bridge role is Asks first, and an employee hired from it cannot go above it. See Hiring a digital employee.