Document Approval Control | Multi Approver Management System | Document Control System | Document Approval System
by Binary Bridge Technology Services https://bbtech.ae$ 39.99
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Manufacturing (mrp) • Purchase (purchase) |
| Lines of code | 2042 |
| Technical Name |
bb_document_approval_control |
| License | LGPL-3 |
| Website | https://bbtech.ae |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Manufacturing (mrp) • Purchase (purchase) |
| Lines of code | 2042 |
| Technical Name |
bb_document_approval_control |
| License | LGPL-3 |
| Website | https://bbtech.ae |
| Versions | 17.0 18.0 19.0 |
Document Approval Control
A premium approval workflow module for Odoo that controls who can approve, confirm, validate, or post critical business documents across departments.
Rules are defined in Settings: you choose the document type (model), the protected action, approvers, and how many approvals are required. Users submit documents for approval; approvers work from activities and approval lines; confirm/post/validate stay blocked on the server until your rule is satisfiedâso governance is not only a visible button state.
What the screenshots show
The images below are taken from this module inside Odoo (Settings, approval rules, rule form fields, amount and options tabs, and security groups). They are not generic stock graphics: each file maps to a real screen so you can see where to configure rules, how lists and forms look, and how access is separated between administrators and approvers. The workflow banner is a single overview graphic illustrating the end-to-end path from submission to authorization.
Built For
Teams that need controlled approvals, internal governance, and traceable decision workflows before business actions are completed.
Use it when sign-off must happen before money moves, inventory is shipped, manufacturing is released, or accounting entries are posted. Multi-level approvals (any approver, all approvers, or a minimum count), optional amount thresholds, and chatter-linked activities give auditors a clear trail without forcing every user through developer menus.
Finance & Accounting
Invoices, vendor bills, entries, and payment posting controls.
Sales & Procurement
Quote/order confirmation routed through manager/CEO approval.
Operations & Manufacturing
Transfer validation, receipts/deliveries, and MO controls.
From Submission to Final Authorization
Users create business documents and submit for approval. Approvers receive activities, approve or reject (optionally with a reason), and protected actions remain blocked until your configured threshold is metâwhether that is one signature, everyone, or a minimum number of approvers.
Rejected documents can be corrected and resubmitted; approved lines and activities update in Odooâs mail layer so nothing depends on informal email outside the system.
This is the moduleâs workflow overview graphic: it summarizes the journey from document creation and submission, through approver notifications and decision boxes, to finally unlocked actions. Use it to explain the process to finance or operations stakeholders before drilling into the Odoo screens that follow.
Requester submits → configured approvers receive activities → threshold approval logic is enforced → action can proceed.
Central Access from General Settings
Administrators enable and reach Document Approval from General Settings, the same area teams already trust for company data and integration options. You do not need a hidden technical menu to maintain who approves which document type.
From here you open the approval rules: create sequences for sales, purchases, invoices, payments, transfers, manufacturing orders, and moreâeach rule binds a model and action to approvers and approval mode for that companyâs policy.
This capture shows the Settings block where Document Approval is turned on and where the shortcut lives to manage rules. It proves the module is discoverable for authorized users and sits beside other business-critical configuration rather than buried in Apps technical lists.
Typical path: Settings → Document Approval → Manage approval rules
Approval Rules You Can Govern
Each rule ties a document type (Odoo model) to a protected action (what must wait for approvalâconfirm order, post invoice, validate transfer, and similar).
You assign who may approve (users and/or groups), how many approvals count as âdoneâ (any one approver, every listed approver, or at least N approvals), and optional filters so different document subtypes or journals can follow different policies. The list view gives a one-screen picture of coverage; the form is where you refine each rule.
The tree view of all approval rules: sequence, target model, guarded action, and approval mode at a glance. Use it to audit that every critical flow is covered and to reorder rules when several could match the same document.
The rule form where admins pick model and action, set approvers and approval mode, and narrow when the rule applies (including document subtypes where relevant). This is the screen your governance team will use most often when policies change.
Route High-Value Documents
Optional amount windows help focus escalation on material thresholdsâso low-value routine documents can flow faster while high-value ones always hit the right approvers.
Define minimum and/or maximum amounts in company currency; rules can combine amount logic with document filters for fine-grained policy.
Shows the amount section on a rule: where min/max boundaries are entered so the same model can require different approval depth depending on monetary exposure. Pair this with approval mode (any / all / minimum count) to mirror your delegation-of-authority matrix.
Activities & Reject Controls
Per-rule options control whether Odoo should create follow-up activities for approvers and whether a rejection reason is mandatoryâuseful for audit and KPI reporting.
These toggles let you balance strict documentation against speed on low-risk flows.
The options area of a rule: flags for activity-driven reminders to approvers and structured rejection capture. What you see here backs the âmailâ and audit storyâapprovers work out of their Odoo activities instead of losing context in external email threads.
Clean Access for Admins & Approvers
Dedicated groups separate who may configure rules from who may approve documents. Assigning users to the right security groups is how you scale approval from a pilot team to the whole organization without opening Settings to everyone.
On each rule you still designate approvers (users or groups); the screenshot opposite illustrates the underlying access rights those roles map to inside Odoo.
- Administrator configuration rights
- Approver groups aligned to business roles
- Server-side enforcement of protected actions (not just UI hiding)
A view of the moduleâs access groups (typical Odoo Users form or implied rights): which profiles can maintain rules versus perform approvals on documents. Use it with your IT policy to document segregation of dutiesâconfiguration stays with administrators, execution stays with approvers.
Adapter-Ready for Custom & Third-Party Apps
The module includes a core approval engine plus model adapters for standard Odoo documents. The engine handles rules, approval lines, thresholds, activities, and server-side blocking; each adapter is a thin bridge to the correct buttons and methods on that model.
Your own modules (or third-party apps) can register additional adapters so custom models participate in the same submit / approve / reject / approve-and-continue flow without copying the whole engineâideal when you extend Odoo with proprietary document types.
Core Engine
Rule resolution, approval lines, activities, thresholds, and action guards in one reusable layer.
Thin Adapters
Minimal integration code for model-specific buttons/methods and document subtype logic.
Scalable Governance
Extend approval controls to new custom documents without redesigning your approval architecture.
Complete Feature List
Rule Configuration
- Settings-driven approval rule management
- Model/action based protection
- Company-specific + global fallback logic
- Amount-based routing with min/max thresholds
- Document subtype support (invoice/bill/entry)
- Stock subtype support (incoming/outgoing/internal)
- Reorder rules to control evaluation when multiple rules could match
Approval Execution
- Submit for approval button on protected docs
- Approver-specific pending lines
- Approval modes: any, all, minimum count
- Approve, reject, approve-and-continue actions
- Resubmit after rejection workflow
- Server-side hard block until approval complete
- Chatter updates when status changes for traceability
Coverage & Extensibility
- Sales, purchase, account.move, payment
- Stock pickings (delivery/receipt/transfer)
- Manufacturing confirmation/completion
- Activity/chatter audit trail per approver
- Adapter registration for custom models
- Designed for future third-party expansion
- Single engineâextend behavior via adapters, not forks
Best Fit For
Technical Specifications
| Specification | Details |
|---|---|
| Module Name | Document Approval Control |
| Supported Odoo | Odoo 17 |
| Core Dependencies | mail, sale, purchase, account, stock, mrp, base_setup |
| Approval Engine | Rule-based mixin + approver line tracking + adapter layer |
| Notification Method | mail.activity per approver + chatter updates |
| Security Approach | Server-side action guards; not only button visibility |
| Deployment | Odoo.sh / On-Premises |
| Typical rollout | Install app, assign groups, enable in Settings, create rules per company, then validate on a staging database before go-live. |
| Edition | Community & Enterprise compatible |
Binary Bridge Technology Services
We build enterprise-ready Odoo modules focused on governance, scalability, and measurable business control across departments.
Please log in to comment on this module