Reusable Engine

One core mixin powers every domain pack: stage preview, submit, approve, reject, notifications, history and company scoping.

Ordered Stages

Define as many sequential stages as you need. Each stage has a custom name and either specific users or a security group as approvers.

Amount Thresholds

Optional rules per stage: apply when document amount is greater-or-equal or less than a threshold, with workflow currency conversion.

Live Stage Preview

Before submit, users see which stages will be Pending vs Skipped based on the current amount. Amount changes refresh the preview.

Flexible Notifications

Set Approver Notify By to None, Activity (To-Do, default) or Email. See the dedicated section below for full behaviour of each option.

Full Audit Trail

Track every stage decision, who approved and when, plus reject date, reject user and mandatory reject reason.

Multi-company

Workflows are company-aware. Prefer a company-specific workflow, otherwise fall back to a shared (empty company) definition.

Applicable Types

Register document families (Sale Order, Vendor Bill, Delivery…) so one model can host several workflow families.

Manager Security

Dedicated Dynamic Approval Administrator group gates the configuration app and menus.

Approver Type: Users

Select one or more specific Odoo users as approvers for that stage. Only those users can click Approve when the stage is pending. Ideal when a named manager, finance controller or department head must personally sign off.

• Pick any active internal users
• Multiple users on one stage: any of them may approve that stage
• Combine with amount rules so VIP users only see high-value documents

Approver Type: Groups

Select a security Group instead of named users. Any member of that group can approve the stage. Best when responsibility is shared (Sales Managers, Accountants, Warehouse Managers) and membership can change without editing the workflow.

• Uses standard Odoo res.groups
• New group members automatically become eligible approvers
• Mix User stages and Group stages in the same workflow

Amount Rule: Greater Than or Equal (>=)

The stage is required only when the document amount is greater than or equal to the threshold you set. Below that amount the stage is automatically Skipped. Use this for escalation: e.g. Director approval only when amount >= 10,000.

• Example: Stage “CFO” with >= 50,000 — runs only on large documents
• Lower stages without a rule always run for every document
• Currency is taken from the workflow; amounts are converted when needed

Amount Rule: Less Than (<)

The stage is required only when the document amount is less than the threshold. At or above that amount the stage is Skipped. Useful for lightweight review of small documents while large ones take a different path.

• Example: Stage “Team Lead” with < 1,000 — only small tickets need that review
• Pair with a >= stage for the complementary high-value path
• Leave the amount rule empty to always require the stage

None

Do not create activities or send emails when a stage becomes pending. Approvers rely on opening the document themselves, filters, or other process follow-up. Use this when you want a silent workflow or already notify outside Odoo.

• No To-Do activities are scheduled
• No approval-request email / chatter notification is sent
• Approve / Reject buttons still work as usual
• Best for demos, internal teams that watch a queue, or custom notification elsewhere

Activity (default)

Creates a standard Odoo To-Do activity for every eligible approver of the current pending stage. Activities appear in the user’s activity tray / Discuss schedule and are linked directly to the document.

• Summary format: Stage name: Review Document Name
• Deadline set to today so the task shows as due immediately
• One activity per approver; duplicates for the same stage are avoided
• When the stage is approved or the flow moves on, related To-Dos are closed
• Ideal when approvers work inside Odoo every day

Email

Posts an approval-request message on the document chatter and notifies the stage approvers by email, including a direct link to open the record. Uses the built-in mail template with stage, document, amount, company and requester details.

• Subject: Approval required: Stage for Document Name
• Body includes workflow name, stage, amount, company, requester and Open link
• Goes through Odoo’s mail queue — a down mail server never blocks Approve / Reject
• Also reaches users who prefer “In Odoo” inbox by forcing the email path when needed
• Ideal when approvers may be offline or outside the app most of the day