What a team lead can and cannot do

A team lead's reach comes from two things working together: which teams you lead, and which software role you hold. The team decides whose leave you touch; the role decides what you can do with it. Here is where the lines fall.

Your scope is your team

You are a lead of a team when you are marked as its lead. That sets your scope: the members of that team, plus any teams nested directly beneath it on the calendar. You act on those people and no one else. Company-wide visibility is a separate permission that leads do not carry, so you will not see or decide leave for other parts of the business.

What a lead can do

The standard Team Lead role can:

• View leave for the team you lead, and your own.
• Approve or reject your team's pending requests.
• Request leave for yourself.
• Cancel your own requests, and cancel a team member's request (handy when someone leaves mid-request or a request was approved by mistake).
• See and upload supporting documents on your team's requests, such as a sick note.

What a lead cannot do

Out of the box, the role stops short of admin territory. A lead cannot view leave across the whole company, record leave on someone's behalf, manage users, teams, roles, leave types or quotas, or open reports and the audit log. Those live with HR admins.

Need something on this list? An admin can add the exact permission to your role rather than handing over full admin access. For example, granting Record leave for others unlocks Record leave on someone's behalf without changing anything else.