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.
The system supports one approver. Reality has line manager → head of dept → finance for anything over £5k. You end up emailing.
Approver's on holiday. Request sits for two weeks. Nobody knew to set a delegate. Trial period misses the deadline.
Finance and HR both need to sign off on a salary change. Sequential is too slow; you want both to see it at once.
Leave requests under 3 days: manager only. 3–10 days: manager + HR. 10+: add the department head. Hard to encode.
See how multi-stage approval chains route a request to the right people — in this interactive demo.
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.
A → B → C. Each approver in turn. Optionally skip ahead if a level is the same person as the requester's manager.
Send to multiple approvers simultaneously. Require all to approve, or any one of them, or a quorum.
Routing depends on the data. Amount-based, role-based, department-based, location-based — combine as needed.
Approvers can set delegates for absence periods. The system routes around them automatically, with audit trail.
No action within X days → ping the approver. Still no action → escalate to their manager. Configurable per chain.
Every step of every chain logged: who approved, when, with what comments, what conditions matched, what escalations fired.
Build the approval structure (sequential, parallel, conditional).
Apply the chain to leave, expenses, pay changes, etc.
New request → system routes through the chain based on the data.
Reminders, escalation, delegation — handled automatically.
Parallel + escalation cut decision time materially compared to email chains.
Above-threshold spend always sees the right approvers. No manual policing.
Requester sees exactly where their request is. No "did you approve that?" Slack messages.
Approval trail attached to every record — ready for SOX, ISO 27001, or any other audit.
HeimdallHR is most powerful when used together.
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.
See how chains route, escalate, and delegate themselves — book a demo or talk to our team and stop policing approval policy by Slack message.
No commitment — we’ll get back to you within one business day.