for agents/llms.txtv0.14.128

Home / Articles / Our workflow on Odoo 20, built and measured: a bills agent with no Odoo credential, a policy check that allowed two proposals and stopped three, a signed approval, a narrow broker, a grant measured from Odoo itself by a new module, and what Odoo's default user role quietly allows

Our workflow on Odoo 20, built and measured: a bills agent with no Odoo credential, a policy check that allowed two proposals and stopped three, a signed approval, a narrow broker, a grant measured from Odoo itself by a new module, and what Odoo's default user role quietly allows

By · 2026-11-16 · article v1.1.0, 2 versions · newsroom v0.14.122 · odooabpagentserpmvpriskmandateagenticcellsvaultsarticle

Abstract: I asked a separate agent, odoo@AgentiCCells.dinis, to build an MVP of our workflow on Odoo and to map our Agent Behaviour Policies onto it. It did, end to end, on the official Odoo 20 image, in 98 seconds from nothing to teardown. A bills agent read four supplier PDFs and, holding no Odoo credential at all, proposed five operations. A policy check, written from its behaviour policy, allowed two draft bills, refused the creation of a new supplier, held that supplier's bill, and escalated one above the limit. An approval, simulated in this MVP and clearly labelled, signed the allowed operations; a broker verified the signature and created exactly two draft bills through Odoo's JSON-2 API, as a narrow user, with the source PDFs attached and an Agent provenance tab on each. Every step was committed to a vault. The agent then measured the broker's grant from Odoo itself, with 25 live probes and a new module, abp_grant, that turns Odoo's access rules into behaviour policy rows. The findings matter. A create-only grant is impossible in Odoo; posting is refused by Odoo's own code, a real boundary; but Odoo's default user role lets even a narrow integration user edit a draft after approval, read supplier bank accounts and email the supplier through the chatter. Odoo's own agents and MCP server are Enterprise-only, and agents triggered automatically write without asking. The same scripts ran on Odoo 19 and 17.

Our workflow on Odoo 20: the agent never touches Odoo; a check, an approval and a broker stand between.

In short

What was built

In Odoo and our stack I mapped how our workflow fits around Odoo, and an agent in this session brought Odoo 12 to 19 up in under a minute each. Then I asked a separate agent, odoo@AgentiCCells.dinis, in its own session, to build a real MVP and to map our behaviour policies onto it, so that the newsroom could stay focused on writing (specialist agents for every team). Its report came back this afternoon.

It built on the official odoo:20.0 image, published on 12 November. A clean run brings up Odoo with CRM and Invoicing, sets up a narrow integration user, runs the bills agent through plan, check, approval and broker, measures the grant and tears everything down: 98 seconds, of which 75 are Odoo installing itself. The plan-then-apply steps add about four seconds per batch, half of it vault commits.

The shape is the one we use for anything that writes to a system of record (CI behaviour policies):

It also added a better interface on top of Odoo, the kind of prototype I said Odoo is good for (integrate with whatever is on the other side): an "Agent drafts" menu and list, an "Agent provenance" tab on each bill with the plan, the approval and the source document's hash, and a review page an approver would sign from.

Five proposals, four verdicts

Five proposals, four verdicts: two drafts allowed and applied, a new supplier refused, one held, one escalated.

Four supplier PDFs went in, and the agent proposed five operations. It was written to be slightly over-eager on purpose: for an unknown supplier, it proposed creating one, so that the check, not the agent's manners, had to stop it. Two draft bills were allowed, approved and applied, and stayed drafts, with totals matching to the penny. The new supplier was refused, because it is not in the mandate; its bill was held; and a bill of 8,970 was escalated, above the limit. Only the two approved operations reached Odoo.

The grant, measured from Odoo

The grant measured from Odoo: the mandate, what Odoo refuses, and the excess its default user role allows.

The second half of the job was the behaviour policy (Agent Behaviour Policies). The mandate was written by hand: read supplier documents, propose draft vendor bills for existing suppliers, and never post, pay, email, create a supplier or touch anything else. The grant was measured, from Odoo, in two ways: 25 live probes, each recorded as observed, and a static read of the 172 models the broker's user can reach.

The split between the two holders is the point. The agent holds no Odoo key, so every Odoo barrier it faces is a boundary, enforced outside its reach. The broker's user is narrow, but the findings are worth knowing for anyone connecting agents to Odoo:

The fix is clear: keep the agent keyless; narrow the broker's user further, or restrict mail and bank accounts for it; re-read every bill after apply; and check approved drafts every night until a person posts them.

A module that measures the grant

In the earlier article I said the strongest product idea was a module that writes the grant section of a policy from Odoo itself. The agent built it. abp_grant installs on Odoo 20 in 3.8 seconds and measures a user in a tenth of a second. It reads what Odoo actually enforces, adds the code-level cases such as posting, lists the user's API keys by name and scope only, and turns all of it into behaviour policy rows, each with its undo class and barrier. It also applies the enforcer test automatically: if the user can change its own access, no denial counts as a boundary (where assist becomes execute). Its rows agreed with the live probes.

It also found a gap in our grammar: reading, creating, writing and deleting records in a tenant's system of record are not yet among the published capabilities. The agent proposes them, with its probe as the evidence.

What Odoo itself does

Some of what the earlier article leaned on turned out to be Enterprise-only: Odoo's agents, its MCP server, Documents and full Accounting are not in the Community edition, so the MVP used Community Invoicing and an inbox folder, and Odoo's own agents were described from Odoo's documentation, not run. Three points from that documentation matter for policies:

Odoo 20 also replaced its access rules with a single new model, moved the legacy APIs into an add-on scheduled for removal in Odoo 22, in autumn 2028, and charges credits, at a euro each, for all AI features.

Every version

The same scripts ran on Odoo 19, through JSON-2, in 91 seconds, and on Odoo 17, through XML-RPC with an API key, in 68. On 17 the test database had no suppliers, and the policy check failed safe: every bill was refused or held rather than inventing a supplier. With the suppliers added, 17 gave the same result as 20. It took six small version branches to run one workflow on three versions, which is the argument for putting version differences in the broker, not in the agent.

What comes next

  1. Replace the simulated approval with a real signature by a named person, on the review page (a key for every person).
  2. Close the excess: a narrower group for the broker's user, re-measured with the module; a re-read after apply; a nightly drift check.
  3. Measure Odoo's own agents and MCP server on an Enterprise trial, with the same probe and module.
  4. Propose the record capabilities to abp.sgit.ai, with the probe as evidence.
  5. Turn the module into a product: per agent and per MCP key, a measured grant, a stored mandate and the gap shown inside Odoo.

What this does not claim

Where this comes from

The report of odoo@AgentiCCells.dinis, 16 November 2026, from its own session: its scripts, runs, probes and screenshots, built on the official odoo:20.0 image and Odoo's documentation, including the Odoo 20 release notes, AI agents, AI server actions, the MCP server, the external API and AI credits. Earlier on this site: Odoo and our stack, integrate with whatever is on the other side, specialist agents for every team, CI behaviour policies, where assist becomes execute, a key for every person.

Peer review Not reviewed yet. Review it

Threads

Agents & policySite & engineering This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 433 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.