A leave request can be approved from two places. Approvals is a queue where you handle the day’s arrivals one at a time. Team absences is a leave board where you see the whole season and can place leave.
The views have different approval buttons, and the undo window exists only in the queue.
| You want to | Use | The approval is |
|---|---|---|
| Handle the day’s requests as a queue | Team → Approvals | Approve leave |
| See the whole season and place leave | Team → Team absences | Approve |
Work the queue
Team → Approvals is one prioritised queue holding everything you need to approve: working time, expenses, trips, leave, shift swaps, open shifts and training. Leave requests wait in the same queue as the other rows.
- Approve leave grants the leave.
- Reject requires a reason: “Tell the employee why…”
- Undo is shown for about ten seconds. If you undo, the decision is not saved at all.
- On the keyboard, A approves, R returns, and J and K move through the queue.
The other rows in the queue work on the same logic: Approve working time.
Approval confirms whole days off. When you grant the leave, whole days off that have already passed are confirmed at the same time, in your name — the employee is not asked to confirm a day they were away. Days still ahead are confirmed as each one ends. The days still come to you for approval as working time, exactly like working days. A half day off stays with the employee: it has a worked half only they can record.
Place leave on the board
Team → Team absences shows the whole season as a single board. Here the approval is Approve and the rejection is Reject + Rejection reason.
Place and grant exists only on the leave board. With it you record leave placed by the employer, without an employee request.
The leave board has no Undo. The decision is saved the moment you press Approve or Reject. If you want the ten-second undo window, handle the request in the Approvals queue.
Read the staffing signal
The leave surfaces show an advisory Staffing row: it shows the required and the planned number side by side. If a grant takes staffing below the required level, Kelomo warns you – the Granting drops staffing warning tells you how many days it concerns. In the queue the equivalent signal is Coverage impact.
The signal appears only if a planning unit is selected and staffing requirements have been defined. Remember the row’s own note as well: “Staffing reflects planned shifts, not the painted placement yet.”
Staffing does not block a grant. The row is advisory, and the supervisor makes the decision.
Gaps that published shifts do not cover are handled in shift planning under Absence gaps, see Plan and publish the shift roster.
If something goes wrong
You cannot approve your own request. Ask another supervisor or an administrator for the decision.
The rejection will not go through. The reason is mandatory: “Tell the employee why…” Write a justification and Reject will work. The employee sees the reason.
You pressed the wrong button in the queue. Press Undo immediately – the window is about ten seconds, and the decision is not saved at all if you make it in time. The leave board has no equivalent window.
The staffing row is not showing. Either no planning unit is selected or staffing requirements have not been defined. You can grant the leave anyway.