Loading
Module
An employee requests leave from their portal. The manager approves or declines it. The balance updates, the history records it, and the approved days appear on the shared organization calendar where the rest of the team can see them.
What this solves
Leave handled over email or chat has three failure modes, and most teams hit all three. Requests get lost in an inbox, so an employee takes the day assuming silence meant yes. Balances live in a spreadsheet that one person maintains, so nobody else can answer "how many days do I have left" without asking. And the team calendar never learns about any of it, so two people on the same two-person function book the same week off.
The fix is not more process. It is making the request, the decision, the balance and the calendar the same record instead of four copies of it.
What is included
Employees raise their own leave requests from the self-service portal, with the dates and the reason attached. No form to download, no manager to chase.
Managers act on a request directly. The outcome is recorded against the request, so there is always an answer to "who approved this, and when".
Taking leave moves the balance. Employees read their own balance in the portal without asking anyone, and the number does not depend on a spreadsheet being up to date.
Every request, with its dates and its outcome, stays on the record. Useful at review time and essential when someone questions a payroll line.
Approved leave lands on the same organization calendar that carries meetings and events, so an absence is visible before someone schedules over it.
Leave days and attendance days are computed from the same organization timezone, so an approved day off and a missing attendance record describe the same date.
Leave is one of the places where permissions matter most. Employees see their own requests, their own balance and their own history — never anybody else’s. Managers see what their team role grants them, which you configure in workspace settings with permission presets rather than by hand-assigning capabilities one at a time.
That boundary is not enforced by the screen. It is enforced in the database with Row Level Security, which means a query that forgot its filter still cannot return another employee’s leave record. The same rule protects an employee’s leave from a different organization entirely.
Leave shares its records with the rest of the workspace, so these modules read the same data rather than a copy of it.
Sign your organization up, configure your timezone and brand color, and invite your team. You can be running the same day.