Leave overview

Leave brings together requests for time away, their approval progress, and any tracked allowance. Employees request their own leave; authorized managers and HR review it. A submitted request is not approved time off.

Access needed

Access depends on your assigned permissions and workflow scope.

Read your own requests and submit leave: leave.requests.submit
Sign in with an account linked to your employee record. This grants only your permitted own-data scope. Editing and cancelling additionally follow ownership, status, first-approval and start-date rules.
Role and permission labels
Typical responsibility: Employee. Role names alone do not grant access.
Submit and maintain leave requests
Read the employee request list: leave.requests.read
Role and permission labels
Typical responsibility: HR or authorized reader. Role names alone do not grant access.
Read employee leave requests
Use the approval queue and take an assigned manager step: leave.requests.review
The queue requires an employee link. The request must be assigned to you or covered by an active leave delegation. Own requests cannot be reviewed.
Role and permission labels
Typical responsibility: Manager or active leave delegate. Role names alone do not grant access.
Review leave requests
Review unassigned manager-stage requests or an HR stage: All:leave.requests.reviewleave.requests.approve
The HR stage needs a different person from the first approver. The linked approval queue excludes own requests. A role title alone is insufficient.
Role and permission labels
Typical responsibility: HR reviewer. Role names alone do not grant access.
Review leave requests
Take HR leave approval steps
Read your own balances and ledger: Sign in with an account linked to your employee record. This grants only your permitted own-data scope. No administrative balance-read permission is required. Only policy-backed types have tracked balances.
Role and permission labels
Typical responsibility: Employee. Role names alone do not grant access.

Demo screenshots may show broader access than your account.

Choose your starting point

Area	What it is for
My Workspace → Leave	Request your own leave and check your requests, balances, and history.
Leave → Requests	Authorized staff review permitted employee requests and arrange changes.
Leave Approvals	Eligible reviewers decide requests assigned or available to them.
Leave → Calendar	Check permitted team or organization absence dates.
Leave Types and Balances	Authorized staff configure leave categories and balance policies or investigate allowances.

Start with Request leave for the employee workflow. Continue with Review leave requests for manager and HR decisions. Use Leave balances and policies for recorded allowances, history, policy settings, and authorized adjustments. Use Leave calendar to check permitted coverage and inspect dated entries.

Use Leave types to maintain categories and their request limits.

Use the Leave Activity log to investigate recorded actions and compare changes.

Understand the key distinctions

A leave type identifies the category and whether it is paid or unpaid. Its maximum days per request is different from an annual allowance. A balance policy defines tracked entitlement and accrual; a type without a balance policy has no tracked balance check.

Working days follow the applicable workspace calendar and holidays. A date range can contain more calendar days than the request's working-day count. Always check the request preview.

Approval can use one manager step or manager followed by HR, depending on the flow stored on the request. Employees cannot approve their own requests. A first approval in a two-step flow is not final approval.