Apps › Control access and audit

Approval Workflow for Odoo Community

Types of request, the ladder of people who approve each one, and a decision log nobody edits: who was asked, who clicked, when and why.

Open the live demo Read the manual

Odoo 16Odoo 17Odoo 18Odoo 19Odoo 20

A spending request of the demo for a replacement extraction fan: its questions answered, the first step done and Two of the board waiting
A spending request of the demo for a replacement extraction fan: its questions answered, the first step done and Two of the board waiting
Runs onOdoo 16 to 20Community or Enterprise, self-hosted or Odoo.sh
NeedsOdoo onlyno Enterprise module
Price89 EURone-time, per series, on the Odoo Apps Store
Demodemo20.bambooforge.devlogin page already filled in
Supportsupport@bambooforge.devfirst reply within one business day
Version20.0.1.5.2bambooforge_approvals

136 automated checks run before every release of this app, the same suite on every series it ships for. The complete list is in the source you receive; run it yourself with --test-enable.

For the people who decide

What your managers see

Approvals > Reporting is the approval administrators' menu. Each analysis opens on a chart, with the pivot one click away, and the pivot downloads to Excel from its toolbar.

Requests

requests by type and outcome, with their amounts.

The director sees what the company asks for, and how much of it is refused.

Approver Decisions

each approver's decisions: the days they take once it is their turn, averaged, the decisions made after the step's deadline, and what waits on whom now.

The process owner sees who keeps requests waiting, and where the deadlines are too tight.

How you use it

What people do with it

Flow 01

Define a type and its ladder

For an approval administrator, once.

  1. Approvals > Configuration > Approval Types > New.
  2. Say what the form asks for: an amount, a period, a reference, an attachment, your own questions.
  3. Add the steps in order: a group, named people or the requester's manager, how many must approve, from which amount.
  4. Set Chase after, Email approvers, Confidential, Delegation allowed.
The Capital spending type of the demo: what its form asks for, and two steps, Budget holder and Two of the board from 2,000
Flow 02

Raise it, decide it

For the requester and the approvers.

  1. All Requests > New: the type, the amount, the answers; attach the quote.
  2. Submit: the ladder is built and its first step's approvers get an activity and a mail.
  3. Approve, or Refuse with a reason the requester reads.
  4. Who decided lists each decision: who was asked, who clicked, when.
Who decided on a request of the demo: each approver of each step, Approved or Waiting, who clicked and when
Flow 03

Make a record wait

For an approval administrator.

  1. Approvals > Configuration > Approval Rules > New: the model and a condition written like a filter.
  2. The ladder, the amount field, and Blocks: the method of the record's button.
  3. What happens when approved or refused: a field set, an activity, a mail, a server action, a webhook, a message.
An approval rule of the demo: sales orders above 5,000 climb Capital spending, block action_confirm, and post a message, schedule an activity and call a webhook once approved

Price and where to buy

89 EUR, one payment per Odoo series, on the Odoo Apps Store. Pick your series:

Twelve months of support by the people who wrote the code; bug fixes and improvements within the series free for as long as it is published. Report a bug within two months of purchase and, if it is not resolved within fifteen days, you get a full refund. Full source under OPL-1, no licence key, no phone-home. The whole promise.