PTO and leave
The PTO module covers the whole loop: an employee requests leave, a manager decides, balances update and the team calendar shows who is away.
Requests and approvals
Section titled “Requests and approvals”Employees pick a type, a date range and an optional note in the app. The request goes to the people above them in the reporting line and to admins; see Organisation and onboarding. Managers approve or decline from the dashboard or the app, and the decision lands with the employee immediately.
Time off policy
Section titled “Time off policy”Settings, Workspace, Time off policy decides how balances behave:
- Accrual. All at once makes the full yearly allowance available on 1 January. Month by month earns one twelfth each month, and a request can only use what has been earned by the month it starts.
- Proration. Someone with a start date in the current year gets a share of the allowance for the months they work, rounded down to the half day.
- Carry-over. Unused days roll into the next year up to the cap you set; 0 means they lapse on 31 December. Carried days can expire at the end of a month you choose. They are used first, so only the part not booked by then lapses.
- Sick leave. Choose whether sick days reduce the holiday allowance or are tracked separately.
Every balance shows the yearly allowance, what is earned so far, days carried over and what is still available. Admins change an individual allowance under Time off, Allocations.
The team calendar
Section titled “The team calendar”The dashboard renders a month grid with approved leave as solid entries and pending requests as outlined ones. German public holidays are computed directly, including the movable feasts, so nobody plans a sprint over a holiday again.
Reminders
Section titled “Reminders”Live notifications reach the dashboard over WebSockets the moment a request arrives, and the app is updated the same way.