Multi-level approvals
Build approval flows with several levels, triggered by rule and value band. Each decision is logged in an immutable trail, and the process advances level by level with notifications.
- Approver chain by rule/value
- Level-by-level approval with notification
- Append-only decision log (point-in-time)
The rule picks the path
Approval chains trigger by value or rule and each request takes the right route without you remembering to forward it.
Level by level, no gaps
Each step notifies the right approver and nothing advances without sign-off from someone with authority.
A trail no one can erase
The immutable decision record keeps who approved, when and why: audits with no surprises.
Approver by user or by role
Define approvers by user or by role and the chain stays valid even as the team changes.
Less bottleneck, more speed
Automatic notifications keep requests from sitting idle waiting for someone to remember to look.
Versioned policies: the invoice uses the rule in force at the time
Approvers by user or by role
A decision trail no one edits
Governance that scales
Define approver chains by value and condition. The request escalates automatically and notifies the next approver.
Traceable end to end
Each approval/rejection is logged: who decided, at what level and when.
- 1
Define the rules and values that trigger each chain.
- 2
Configure the levels and their approvers by user or role.
- 3
Each level is notified and decides in turn.
- 4
The decision is recorded in an immutable trail.
A discount above the limit
The rule fires the chain and the request rises automatically to the level with authority.
An audit asking for the history
The immutable trail shows every decision with author, date and reason, with no gaps.
An approver on vacation
With approvers by role, the request goes to whoever holds the role, without stalling.
How does a multi-level approval chain work?
You define approvers by rule and value band, and the request escalates automatically level by level until it reaches whoever has authority.
Does the system notify the next approver on its own?
Yes. Each step automatically notifies the right approver, with no need to forward it manually.
Can I set approvers by role instead of by person?
Yes. Approvers can be defined by user or by role, and the chain stays valid even as the team changes.
What happens if the approver is on vacation?
With approvers defined by role, the request goes to whoever holds that role at the time, without stalling.
Can approval decisions be edited afterward?
No. The decision log is append-only and immutable, keeping who approved, when and at what level.
Does this help with an audit?
Yes. The immutable trail shows every decision with author, date and level, ready for whenever an audit asks for the history.
Can I have different rules for different value ranges?
Yes. Approval chains trigger by value or by rule, so each request automatically takes the right route.
Is the rule applied always the latest one, even for old requests?
No. Policies are versioned by effective date, so each approval uses the rule that was in force at that time.
Does this stop requests from sitting idle waiting for someone to notice?
Yes. Automatic per-level notifications cut the bottleneck of requests forgotten in an inbox.