Approvals that match your org
Single-approver workflows are fine for small teams. Once you grow, you need sequential chains, parallel approvers, conditional routing, delegation, and escalation. This add-on gives you all of it without the spreadsheet of who-approves-what.
Sound familiar?
One-size-fits-all
The system supports one approver. Reality has line manager → head of dept → finance for anything over £5k. You end up emailing.
Delegation gaps
Approver's on holiday. Request sits for two weeks. Nobody knew to set a delegate. Trial period misses the deadline.
Need parallel approvers
Finance and HR both need to sign off on a salary change. Sequential is too slow; you want both to see it at once.
Conditional rules
Leave requests under 3 days: manager only. 3–10 days: manager + HR. 10+: add the department head. Hard to encode.
Every kind of approval chain you actually need
Multi-Level Approvals adds sequential chains, parallel approvers, conditional branches, delegation, and escalation rules to every approval flow in HeimdallHR — leave requests, expense claims, pay changes, hires, anything. Build the chain once, attach it to a request type, and it routes itself based on the data.
Everything you need
Sequential chains
A → B → C. Each approver in turn. Optionally skip ahead if a level is the same person as the requester's manager.
Parallel approvals
Send to multiple approvers simultaneously. Require all to approve, or any one of them, or a quorum.
Conditional logic
Routing depends on the data. Amount-based, role-based, department-based, location-based — combine as needed.
Delegation
Approvers can set delegates for absence periods. The system routes around them automatically, with audit trail.
Escalation rules
No action within X days → ping the approver. Still no action → escalate to their manager. Configurable per chain.
Full audit
Every step of every chain logged: who approved, when, with what comments, what conditions matched, what escalations fired.
How it works
Define a chain
Build the approval structure (sequential, parallel, conditional).
Attach to a request type
Apply the chain to leave, expenses, pay changes, etc.
Request flows
New request → system routes through the chain based on the data.
Escalation if stalled
Reminders, escalation, delegation — handled automatically.
The impact
Faster decisions
Parallel + escalation cut decision time materially compared to email chains.
Controls applied automatically
Above-threshold spend always sees the right approvers. No manual policing.
Visible status
Requester sees exactly where their request is. No "did you approve that?" Slack messages.
Audit-ready
Approval trail attached to every record — ready for SOX, ISO 27001, or any other audit.
What's included
Sequential approval chains Parallel approval chains Quorum / any-one approval rules Conditional routing (amount, role, dept, location) Multi-criteria conditions (combine with AND/OR) Approver delegation (planned and ad-hoc) Out-of-office detection Escalation rules with configurable timing Reminder cadences Skip-self protection Applicable to all HeimdallHR request types Approval comments and reason codes Full audit trail Mobile approval UX
Works seamlessly with
HeimdallHR is most powerful when used together.
Common questions
Yes. Skip-self protection prevents anyone from approving their own request, even if the chain would route there. The next valid approver is used instead.
Escalation rules route to the next level. If that fails too, the request goes to a configurable fallback (e.g. HR business partner) so requests never stall indefinitely.
Yes — each approver sees the prior steps, comments, and any conditions that routed the request to them. Full transparency.
Yes. Conditional routing on country, legal entity, or any other attribute lets you operate region-specific approval policies from one config.
Make approvals match your org
Start your 30-day free trial and stop policing approval policy by Slack message.
No credit card required. Cancel anytime.