A team is a named group of people with a set of projects attached. Anyone in the team gets access to every project the team covers, at the role the team sets.
It is a shortcut, not a separate permission system. Everything a team does could be done by granting each person each project by hand — teams exist so you stop doing that.
Who this is for
Agencies past roughly five people or ten projects, where the same handful of specialists work the same handful of accounts. Below that, granting projects directly on the invite is simpler and you should stay there.
The signal you need teams: you are about to grant the same four projects to the third person this month.
How to set one up
Name it after the group of people, not the work — "Retail pod", "Enterprise team", "Contractors". Add the people, then attach the projects with a role.
The role is set per project on the team, so one team can be editor on the accounts it runs and viewer on an account it only reports against.
Onboarding and offboarding
This is where teams pay for themselves.
A new client — attach the project to the team once, and everyone who works that book of business has it. No going through the roster.
A new hire — add them to the team and they have every account that team covers, at the right role, immediately.
Someone leaves — remove them from the team and all of it goes at once. This is the important one: hand-granted access is what gets forgotten, and forgotten access on a client account is the kind of thing you find out about badly.
When someone is in two places
If a person has both a direct grant on a project and access through a team, the stronger role wins. Someone who is viewer through a team and editor directly is an editor.
This is deliberate: a specific decision about one person should not be quietly undone by a group setting, in either direction.
An empty team grants nothing
A team with people but no projects gives its members no access at all. It does not accidentally widen anyone, and it does not accidentally restrict anyone either.
What teams do not do
They do not change workspace roles. A member added to a team is still a member; a billing contact added to a team still reaches no projects, because their workspace role refuses projects regardless of grants.
They also do not affect billing. There is no per-team charge and no seat count.
Next
- People and access
- Credit budgets
- Projects, and what belongs in one