Teams

Grant a project once, to a whole group. Teams let you hand out access by team name instead of clicking through eleven people one at a time.

Say Dundler Paper’s backend crew needs write access to the Warehouse Service project. You create a Backend team, add Dwight and Darryl, and grant that team one role. When someone joins the crew later, you add them to the team — every project the team reaches opens up at once.

Note: Teams aren’t available on the Free plan. See Plans & Billing.

Create a team

Prerequisites: You need to be a workspace Admin or the workspace Owner.

1. Open Settings → Members → Teams.
2. Select Create team.
3. In Name, enter what the team is called.
4. Under Team members, search for a workspace member and add them.
5. Select Create team.

A new team starts empty and grants nothing by itself — it’s a list of names until you attach it to a project. Only workspace members can be added; every member can see the team list and rosters, but only Admins can change them.

Give a team access to a project

Team access is managed on the project, right next to individual collaborators — both appear in one access list.

1. Open the project’s Overview → Contributors.
2. Select Add Team.
3. From the team dropdown, select the team.
4. From the Role dropdown, select Write, Write and Delete, or Admin — the same roles a person can hold.
5. Confirm.

The team then appears in the access list with a Team badge. Change its role from the dropdown on that row, or remove it with the trash icon. A team holds one role per project.

Keep in mind: A team grant is indirect. Once a team holds a role, everyone added to that team later gets it too — so granting Admin to a team makes every future member a project admin.

Project admins manage their own project’s team access without being workspace Admins. Editing the team itself — its name and roster — always takes a workspace Admin. A roster change reaches every project that team touches.

How roles combine

A person’s effective role on a project is the highest of everything they hold: their own collaborator role plus every team grant that reaches them. Teams only ever raise access, never lower it.

If Pam holds Write personally and her team holds Write and Delete, she gets the higher one. Leaving the team drops her back to her own Write — a personal grant survives team membership.

To see how it resolved, expand View effective access under the contributor list. It names everyone who can reach the project and where their access came from: a team, a personal grant, or their workspace role. So when you wonder why Creed can edit here, the answer is on screen.

Removing someone from the workspace removes them from its teams. Deleting a team removes its project access everywhere.

What’s next?

Team Roles & Permissions — Workspace roles: what Admins and Members can do.

Project Collaborators — Individual access to a project.

Project Access Control — Project access levels for everyone else.