Leave management lets you define leave types, track balances and run requests through an approval chain that follows the org chart. Employees request from /people/leave; HR configures policy in People > Policies and HR setup.
Defining leave types
- Name and colour (vacation, sick, parental, unpaid and so on).
- Allowance: days per year, with optional accrual through the period.
- Paid or unpaid, which controls whether payroll deducts the day.
- Whether a balance carries over and the maximum carry-over.
- Whether the type needs supporting documents, such as a medical note.
Requesting leave
- 1Employee opens People > Leave and chooses Request leave.
- 2Pick the type, dates and an optional reason. The remaining balance is shown before submitting.
- 3Submit. The request is created with a pending status and routed to the first approver.
- 4Each approver approves or rejects with an optional comment; the requester is notified at each step.
- 5On final approval, the balance is reduced and the days appear on the team calendar.
How routing works
Leave uses the LEAVE_REQUEST approval chain. By default the first step is the reporting manager, from the org chart; HR can add a department head or a specific person. See the approval chains article for step options and SLAs.
Rejected or cancelled requests return the days to the balance automatically. Approved leave that is later cancelled by HR does the same.
Changes to a leave type affect future requests. Requests already approved keep the rules they were approved under.