Skip to main content

Approval flows: who approves what, and in what order

An approval flow decides who must say yes before a request goes through. Set conditions on leave type and day count, target who it applies to, choose an approver by person or by role, and chain steps as any-one, all or sequential.

An approval flow decides who has to say yes before a request goes through, and in what order. ✅


What you can set

  • Conditions — a flow can apply only to certain leave types, or only above a certain number of days. A single day off can go straight through while a two-week holiday needs sign-off

  • Targeting — which people the flow applies to

  • The approver — either a named person or a role

Choosing a role rather than a named person is the safer setup, because the flow keeps working when that individual leaves.


More than one approver

A flow can have several steps, and each step is one of three kinds:

  • Any one — the first approver to respond settles it

  • All — every approver must approve

  • Sequential — approvers are asked one after another, in order, so the second only sees it once the first has approved


Approval flows are not only for leave

Course sign-offs use the same mechanism. A sign-off is routed by an approval flow with the approver set by role, so it does not have to be the learner's own manager who signs them off. If you are waiting on a sign-off, check which role the flow points at.


💬 If a request has been sitting unapproved, look at the flow's approver first. A named approver who has left the business will hold everything up. 🙏

Did this answer your question?