Approvals - Requests & Multi-step Approval Workflow
by Jhon Jairo Rojas Ortiz https://www.linkedin.com/in/jjro$ 89.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 316 |
| Technical Name |
jjro_approval_workflow |
| License | OPL-1 |
| Website | https://www.linkedin.com/in/jjro |
| Versions | 16.0 17.0 18.0 19.0 |
Approval Workflow — Requests, Sign-off & Multi-level Approval
A standalone approval workflow for Odoo. Route every request through multiple approvers, from draft to approved — no code, no other apps required.
Stop chasing approvals over email and chat. This lightweight approval workflow lets anyone on your team raise an approval request, sends it to the right approvers, and enforces a minimum number of approvals before a request is marked as approved.
Perfect for expenses, purchases, time off, contracts, discounts — any internal process that needs a clean sign-off. It depends only on Odoo base: it adds its own app and never modifies your other models.
Requests routed through one or more approvers, each with a clear status (To Approve / Approved).
All requests in one place — with category, requester and current status.
Features
- Approval categories — create a category per process (Expenses, Purchases, Time Off…) with its own approvers and rules.
- Multiple approvers — assign as many approvers as you need for true multi-level approval.
- Minimum approvals — set how many approvals are required before a request is approved.
- Approve / refuse — approvers act with one click; a single refusal marks the request as refused.
- Clear state workflow — To Submit → To Approve → Approved / Refused, plus Cancelled and Reset to draft.
- Optional amount — capture an amount on requests when the category needs it.
- Ready-made views — My Requests, To Approve and All Requests, with filters and group-by out of the box.
- Standalone — depends only on Odoo base; no dependency on other apps.
How it works
- In Approvals > Configuration > Categories, create a category and choose its approvers and the minimum number of approvals.
- Users open Approvals > My Requests, create an approval request, pick a category, fill in the details and submit.
- Approvers find it under Approvals > To Approve and approve or refuse it.
- Once the required number of approvals is reached, the request is automatically approved.
Permissions & data security
Built to respect Odoo's access model — audited so nothing leaks between users or companies.
- 🔒 Private by default. You only see the requests you raised or that you must approve; managers see everything. Approvals can't be forged — a user can only sign off their own line.
- 👤 Role-based access. The app respects Odoo's access groups — there is no portal or public exposure. Everything computes on your standard data through the app's own service, so no restricted field is ever surfaced.
- ✅ Secure by design — audited access model. Audited across the whole suite.
Keywords: approval workflow, approvals, sign-off, multi-level approval, multi-step approval, request approval, approval requests, approvers, approval process, Odoo approvals, purchase approval, expense approval, leave approval, document approval, approval matrix, approval chain, authorization, internal control, request management, no-code approval.
Palabras clave: flujo de aprobación, aprobaciones, aprobación multinivel, aprobación en varios pasos, solicitud de aprobación, solicitudes de aprobación, aprobadores, proceso de aprobación, aprobaciones Odoo, aprobación de compras, aprobación de gastos, aprobación de vacaciones, aprobación de documentos, matriz de aprobación, cadena de aprobación, autorización, control interno, gestión de solicitudes, aprobación sin código, flujo de trabajo de aprobación.
Works with Odoo Community and Enterprise, versions 16 to 19.
More from the author: Aski — ask your Odoo in natural language by chat or voice. aski.dev
Questions, or want a quick personalized demo? Email me at jhonrojas.dev@gmail.com — I am happy to answer questions or set up a short demo.
Support: jhonrojas.dev@gmail.com · License: OPL-1
About the author
Jhon Jairo Rojas Ortiz
Odoo developer · custom modules, integrations & business intelligence
5+ years of hands-on Odoo experience — building and shipping real modules, integrations and analytics for companies across LATAM and Europe. Every app I publish is maintained and supported personally.
Custom Odoo modulesIntegrations & APIsBI & analyticsOdoo 14–19
inConnect on LinkedIn →| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 316 |
| Technical Name |
jjro_approval_workflow |
| License | OPL-1 |
| Website | https://www.linkedin.com/in/jjro |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module