Approving your team’s leave — the first stage

Team lead isn’t a role toggle — it comes from your team: whoever carries the “Leader” mark on a team leads it (set by administrators in Teams). With it you get:
Each vacation type defines its approval path. When it includes the team lead, requests from your team stop at the TL stage first — after you approve, they continue to the vacation manager (if the type requires it) or become approved. You can’t approve your own requests; another approver handles those.
Requests lists what’s pending, each row showing the requested type by its own icon and colour. Act on rows with the TL chip — rows showing VM have already passed you and sit with the vacation manager (no buttons for you). Filter the list by status, employee or leave type — and by team, if you lead more than one. Opening the page with nothing left to approve takes you to Entries with a note that it has already been handled, instead of a dead page; a queue you have filtered down to nothing yourself just stays empty.

Before approving, glance at the Calendar — names are visible to you, so team overlaps are easy to spot. The employee is notified automatically at every step.


Two more tabs open up for you, both scoped to your team — the people on teams you lead, plus yourself. Nobody else appears, whatever you type in the address bar.
Vacations → Report is a matrix: one row per team member, one column per leave type, plus totals and the current balance. Cells show used leave as working days; a +N marks requests still pending in that window. Click a cell to see the leaves behind the number.

Vacations → Balances answers the question you actually have while approving: can this person afford it? Pick a team member in Employee and you get their available balance, what has accrued, what has been used, and the full statement of every accrual and deduction. Year report saves it as a PDF.
The same figure also rides along in the request itself, so during approval you see the balance without leaving the dialog.
You can look at your people’s balances, not change them. Manual corrections — adding or removing days by hand — are the vacation manager’s job.

Leave is personal data. You see it for the people you lead because you decide on their requests — not for the rest of the company. Sick-leave days show as their own column, so treat the report as confidential.
| Subject / title | When |
|---|---|
| Leave request awaiting approval | Someone in your team requested leave that needs your stage. |
| Leave request needs manual approval | A flagged request — includes the auto-reject deadline. |
| Leave request needs a decision | Reminder while a flagged request still waits (every ~8 h). |
| “<Name> checked in late” | A team member checked in after their shift started — visibility, no action required in the app. |
E-mails arrive within a few minutes and use the same titles as the in-app notifications; tune the channels in Notifications → Preferences. Time corrections and self-reported hours are handled by time managers — if a team member’s hours look wrong, point them to “Log time” (Employee Web Guide) or escalate to your time manager.
HR.Click — Team Lead Guide · v1.1 · August 2026. Product screens shown with sample data; names of persons are fictitious examples.