Teams and team leads

Teams group your people so approvals route to the right person and leads see the right calendar. You manage them under Settings > Teams with the Manage teams permission. A team can sit under a parent team, so your structure can mirror how the company is actually organised.

Create and organise teams

Choose Add team, give it a name, and optionally pick a parent team to nest it under. Rename a team from its menu at any time. Deleting a team is safe: its members are simply left without a team, and any sub-teams are lifted up rather than deleted with it. Nobody loses their records.

Assign a team lead

Open a team and use Add lead to promote one of its members. The person must already be in the team; assigning them as lead does not move them across teams. A team can have more than one lead, which is useful for cover or for jointly run teams. To step someone down, remove them as lead and they return to being a regular member.

The Teams page flags any team that has no lead. Leaderless teams fall back to notifying everyone who can approve leave, so it is worth clearing that warning.

What being a lead does

Lead status is set on the team membership, not the software role. That is deliberate: a Backend Engineer can lead a team, and holding the Team Lead software role does not by itself make someone a lead of any specific team. Leave requests from a team route to that team's leads for approval, and leads see their team on the calendar and in reports. For the full picture of what a lead can do, see What a team lead can and cannot do.

What a person is allowed to do across the app is a separate question, answered by their software role and its permissions. See Software roles and permissions.