Team admins and members

Teams have two roles: Team admin and Team member.

These roles control who can manage a team’s membership. They do not replace workspace roles, and they do not automatically grant access to plans.

Team roles

Role	What they can do
Team admin	Add members, remove members, and change team roles
Team member	View the team and its members

Workspace owners and admins can manage any team, regardless of their team role.

Team admins

Team admins can manage the people in their team.

They can:

• Add existing workspace members to the team

• Add many members at once by pasting one email per line

• Remove members from the team

• Change someone’s role to Team admin

• Change someone’s role to Team member

• Use bulk actions to update or remove multiple members

When someone creates a new team, they automatically become a Team admin for that team.

Team members

Team members can view the team, but they cannot manage membership.

They cannot:

• Add people to the team

• Remove people from the team

• Change team roles

• Use bulk member actions

When someone is added to a team, their default role is Team member.

Adding members in bulk

Team admins can add many existing workspace members at once.

To do this:

1. Open the team.

2. Go to the Members tab.

3. Click Add members.

4. Paste one email address per line.

5. Confirm the members to add.

Only existing workspace members can be added this way. If someone is not already in the workspace, invite them to the workspace first.

Last admin protection

Every team should have at least one Team admin.

Tability prevents changes that would leave a team without any admins, such as:

• Removing the last Team admin

• Changing the last Team admin to Team member

If you include yourself in a role change or removal, Tability may ask you to confirm because you could lose access to team admin controls.

Teams and plan access

Team roles are separate from plan permissions.

Being a Team admin does not automatically give someone edit access to plans. Plan access is controlled by plan permissions.

For example:

• A team can have View access to a plan.

• All members of that team can view the plan.

• Team admins still cannot edit the plan unless the team or person has Edit access.

Use team roles to manage team membership. Use plan permissions to manage access to plans.