Leave Approvers

Open this screen in Saral/hr/leave-approvers

Where each person's leave requests go. Three tiers, read in order: a personal approver set on the person always wins; a project approver catches anyone on that project with no personal row; the company default catches everyone else — and a person with none of the three falls back to every Admin. The subject is the person, not the assignment: the People table shows each worker's resolved route, the checker beside it walks the three tiers for one person, and the four tiles are also filters.

You enter

A personal approver and backup for a person (or several at once from the table's bulk bar), with the scope — everything, or holiday and TOIL, or absence only — and whether the approver may book for them.
A project approver and backup, with the same scope, for everyone on that project without a personal row.
The company default — one person for everything, or one each for holiday & TOIL and absence.
The approver pool — who may be offered as an approver — and a CSV import of person, approver and backup.

Saral fills in

Each person's resolved route for holiday & TOIL and for absence: which tier answered, who the approver and backup are, and whether they can book for them.
The coverage tiles — people covered, no personal approver, approve-only, agency absences-only — from the same resolver the leave register uses.
On the Projects tab, how many people each project row actually routes and who on the project is overridden by a personal row; on Company defaults, the list of people who fall through to it.
Approver change requests a worker made from their own leave page, and approvers whose login was deleted while still assigned.

It produces

The approver every new leave request is sent to, and the backup used when the approver is on leave.
A CSV export of every person with their routes, approvers, backups and booking switch.

What this page is for

A leave request has to reach somebody who can decide it, and the wrong somebody is worse than nobody. This page sets and shows that routing for every person in the group, behind the leave.configure key. The leave register, the worker's own page and the approver's queue all read the same resolver, so what the checker shows is what happens.

Three tiers, read in order

Personal first: a row set on the person, for everything or for one kind of request, always wins. Project second: anyone on the project with no personal row for that kind goes to the project's approver. Company default third: everyone else. A person with none of the three is not blocked — their request goes to every Admin — but the first tile counts them and turns red until each has a route. The scope on a row is the kind of request it answers; a personal row for holiday only still leaves absence to the next tier.

Booking for people, and agency workers

Any approver may book leave for the people they approve. Turning Can book for them off on a personal row stops that person's approvers booking for them — they still decide the requests. Agency workers are paid by their agency, so they have no paid holiday here and only absences can be logged, unless Holiday & TOIL requests is switched on in their profile; the fourth tile lists them.

Keeping it current

A worker may ask for a different approver from their own leave page; the request appears above the People table for a decision. When an approver's login is deleted while still assigned, their rows are listed under Approver pool & import to transfer to a current user, so no request is left with nobody. The backup is used when the approver is themselves on leave.

Where the settings live

Everything on this page is its own owner — the three tiers, the pool and the import live here and nowhere else. What needs approval at all, reminders, the weekly digest and approving lapsed requests are HR → Settings → Leave & Absence. Whether a worker may request holiday and TOIL is on the worker's profile.

Next screen: /hr/reports/bradford

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.