Guide, 8 Nov 2026, read 8 Nov 2026
Who should approve what
The four approver types
- The direct manager: the default, and the one that breaks the week the manager is away.
- A skip-level: for requests above a threshold, so the manager's own time off and the long absences get a second pair of eyes.
- A role or a people field: the People partner for the group, the finance partner for the entity, read from the record rather than named.
- A named person: the CFO for a relocation package, the chair for an executive's equity.
Chains and order
A chain is approvers in sequence, and the sequence matters: the skip-level before the People partner for a promotion, Finance after both for the pay change. Approval chains are documented on thirteen rows; the sequence as a configurable thing is documented plainly on Workday, Lattice (edit any step), Humaans (multi-step and conditional) and Shapes (approvals in workflows with signatures in order).
What the map says about chosen approvers
Shapes chooses the approver per time-off policy: direct manager, skip-level, a people field, a permission role or a named person (29 Oct 2026). Personio configures approvers per process, Humaans per request type, Factorial per flow, Workday by security group and role, Lattice per step of a chain. Rippling keys policies to any attribute but the per-policy approver choice is not shown; BambooHR routes by manager or admin; ADP and Paylocity route by role.
Write the policy before the flow
The approval policy is a table: request type, threshold, first approver, second approver, escalation after N days. Write it first, then build the flow from it; a flow built without the table encodes whoever was in the room.
Sources
- Shapes: choose who approves each time off policy, read 8 Nov 2026
- Personio: approval processes, read 8 Nov 2026
- Humaans: requests and approvals, read 8 Nov 2026
Last reviewed 8 Nov 2026.