/settings/erp/people/leave (the Leave Types tab)
Leave types are defined per tenant. The same type can then be used by policies that are scoped to a particular business, so a multi-business organisation usually keeps one shared list of types and varies the policies.
📷 Screenshot: the Leave Settings page with its Leave Types / Leave Policies / Entitlements / Leave Periods / Block Lists tabs — to be added.
Creating or editing a leave type
On the Leave Types tab choose New Leave Type (or click an existing type to edit). The form is grouped into sections; only the name is required, and the optional rules only show their detail fields once you tick the relevant box.Basic info
Accrual settings (Earned Leave)
Tick Earned Leave (Accrual) to make the type drip days into balances automatically over the year, rather than being allocated as one lump.Carry forward
Tick Carry Forward to let unused days roll into the next leave period.Encashment
Tick Allow Encashment to let this type be paid out as cash.
(The encashment workflow itself is covered on the Leave encashment page.)
Limits & restrictions
These guard how and when the leave can be taken. All are optional; leave blank to disable.Flags
The form stops invalid combinations. Ticking Compensatory clears Earned Leave (and vice-versa); ticking LWP clears PPL (and vice-versa). Carry-forward % must be 0–100, the salary fraction 0–1, and the numeric limits cannot be negative — the form rejects values outside these ranges.
Deleting a leave type
Deleting a leave type is a soft delete — the record is hidden, not erased, so historical balances and ledger entries that reference it stay intact. The name then becomes free for reuse.Leave policies (the approval layer)
A leave policy is the companion object that adds the rules deciding how a request is handled — the notice period, the longest stretch allowed, and whether an approver is required. Today’s policy form is deliberately short: Name, Description, Min Days Notice, Max Consecutive Days, Requires Approval, and Active. Accrual and carry-forward rules live on the leave type, not the policy.Adding a leave type does not create a policy, and the Leave Policies tab has no field that lists or selects leave types — so a new type will not “appear” under policies. Types and policies are two independent lists today; you create each separately and bring them together when you allocate. This is covered in full on the Leave policies page.Managing policies needs
hr:admin. You’ll find them on the Leave Policies tab of the same settings page.
Because policies — not types — are what employees actually hold balances against, the names shown on the leave list, the calendar, and the apply form come from the policy name. Name your policies clearly (e.g. “Annual Leave”, “Sick Leave”) so they read well everywhere.
No gender or eligibility rule. Neither a leave type nor a policy can be restricted to one gender — you cannot mark “Maternity” as women-only and have the system enforce it. The only built-in gate is Applicable After (days) above. Keep gender-specific leave on the right people by only allocating it to them. See Leave policies → Eligibility and gender restrictions.
The other tabs
- Entitlements — the standing per-policy day allowance that feeds allocation. Managed with
hr:admin. - Leave Periods — the calendar windows (usually a year) that balances and carry-forward roll against. See Leave periods.
- Block Lists — date ranges (e.g. year-end freeze) when leave of certain types is blocked, optionally with roles allowed to bypass. See Leave block lists.
Permissions
Related
- Leave overview — how the pieces fit together
- Leave policies — the approval/notice layer and how it relates to a type
- Leave allocations (control panel) — turn types/policies into real balances
- Leave periods — the windows balances roll against
- Leave block lists — freeze leave over set dates
- Leave encashment — pay out unused leave
- Holiday lists — how holidays interact with leave types