Teams & divisions
How people are grouped, and what a team card tells you.
Teams group people who work together. Divisions group teams. Together they're the backbone of who gets what - project access, meeting invitations and even extension scoping can all be set by team or division rather than person by person.
Where the new organization tools are switched on, divisions and teams are two of several levels: there are departments between them and groups outside the tree, every level can be renamed, and a team's lead is also the fallback for who your manager is. See Levels and labels and Roles and the chain of command.
The Teams page
/app/teams shows divisions → teams → people (Teams is no longer a navigation tab; where the new organization tools are switched on, /app/teams opens Organization → Structure). Each team card carries:
- Its objective - what it's there to do.
- Its specialty - what it's good at, which is what Autopilot routes work by.
- Its supervisors, marked with a star (a team can have more than one).
- A board roll-up scoped to what you can see: projects, open, overdue, done this week.
Two situations are shown rather than hidden: a team with nobody on it, and people on no team at all. Admins also see divisions that hold no teams, because that's usually a gap somebody should close.
Setting them up
- Teams - Org settings → Roles & Teams.
- Divisions - Org settings → Structure. A team belongs to at most one division.
- Teams are on the Team plan and above.
/app/teams is about teams; /app/organization is about people, stats, announcements, performance and files. They used to overlap; they don't now.
Workspaces that have the new Organization tab find teams and divisions on Organization → Structure, and /app/teams opens it. See The new Organization tab.