Teams & managers
Group people into teams and give managers visibility into their team's time.
A team groups people so a manager can see, edit, and approve their time — without giving that manager access to the whole workspace. Teams are what the "team" permission scope refers to.
Create, rename, and staff teams from the Teams tab on the Team page — that part needs Manage members & invites. Assigning someone to a team uses the Team column on the Members list. Everyone else still sees the Teams tab, but read-only: the teams they're on or manage, with who's on them.
Create a team
Name it on the Teams tab. Rename or delete it later (deleting keeps everyone's time — they just lose the team).
Assign each person to a team from the Team column on the Members list. A person belongs to one team.
Add one or more managers to the team (anyone at Manager level or above). A crown marks people who manage teams.
What managing a team means
A team's managers can see, edit, and approve/lock that team's time — that's the "team" scope on their role. It's how you let a lead run their group without exposing everyone else's work or the workspace's finances.
A manager can also click into a person they manage on the Members list to see — read-only — that person's role, which clients and projects they can access, and which tabs they see. Changing any of that still needs an admin.
How the team scope fits into the wider permission model.