Dynamic Multi-Level Approvals adds one configurable approval engine that works on any Odoo model. You choose the document and the exact moment that needs sign-off, add as many approval steps as you want, and the module holds the action until every step approves, then completes it for you. Nothing is hardcoded and nothing requires a developer.

Approvers act from a colorful personal dashboard, a bar on the document itself, an email, or a public link, and the engine even reassigns work automatically when someone is on time off. Every decision is recorded with a full audit trail.

Every approver opens My Approvals to see exactly what is waiting, what is overdue, and what they approved this month, with one-click Approve and Refuse on each item.

A pipeline bar sits on top of the gated record showing each step and its status, with Approve and Refuse buttons for the person whose turn it is.

Once the last step approves, the original action is re-run, so here the Sales Order is confirmed and its delivery is created automatically. Nothing is faked or skipped.

A refused document shows the requester a Reset to Draft button, so they can fix it and send it through again, with the refusal kept on record in the chatter.

Each Approval Flow names the model, the gate type and the trigger, so you can see every rule across the whole database at a glance.

Pick the model, the trigger field and value, an optional amount field, and add ordered steps with their approvers. No XML and no developer needed.

An activation flow gates record creation instead of a transition, perfect for new vendors, products or any master data that needs a check before it goes live.

The Requests list shows every approval, who raised it, the current step and whether it is pending, approved or refused.

Open any request to see its approvers, decisions, dates, the source document, and the complete message history, everything an auditor needs.

Turn on time-off delegation and the engine reassigns a pending approval to a delegate or a step backup while the approver is on validated Time Off.

Create an Approval Flow, choose the model and the trigger that needs sign-off, then add as many ordered steps as you want with the approvers for each. Any user action that reaches the trigger is held until every step approves, with no custom code required.

Yes. An action gate blocks the transition, for example a status reaching Confirmed or an invoice about to post, and opens an approval request. When the last step approves, the engine re-runs the original action so its full side effects, like the delivery a confirmation creates, are reproduced exactly.

Use an activation gate. A newly created record is archived and hidden everywhere until the approval is granted, then it is activated automatically. It works even on models that do not have a native archive field, because the module provisions one safely.

Yes. Mark a step as an amount tier and give it a minimum and optional maximum. The step only applies when the document amount falls in that range, so small documents skip the senior approvers and large ones pick them up automatically.

With time-off delegation enabled, the module checks validated Time Off and reassigns the pending step to the approver's personal delegate, or the step's backup approver, and records who it was originally assigned to. Approvals never stall because someone is away.

Use the version selector at the top of this page to pick your Odoo release. Each branch is published as its own listing for that exact version, and the module works on both Community and Enterprise.

The team behind this module

About CODEerts

Full-Service Odoo ERP Agency  ·  Solutions That Scale

Every module in our store is built from real client work, tested in production and maintained long-term by a team of Odoo certified consultants. When you need more than an app, we deliver the full solution.