Who can use a project

A project's Settings and access tab (owners change it; others see it as Access) has one list, Who has access, with each entry's type and role. Add access adds a Business unit, a Team or a Person:

Entry	Who has access	Shows next to their name
Business unit	Everyone placed in a connected unit, or in a unit below it (directly or through a team).	Via Customer Service (the unit's name)
Team	Every member of the team, while they are in it. See Teams.	Via and the team's name
Person	People added by name, whatever unit or team they are in.	Manually assigned

Each unit and team gives a role, and so does adding someone by name. Below the list, People shows everyone once, with every way they have access; their role is their own if one was set, otherwise the strongest one they get.

Access ends when the last way goes:

• Disconnect a unit, or remove a team, and everyone who had access only through it loses it; the others keep theirs.
• Someone moved out of a unit (Settings → Users), out of a team, or a unit or team that is deleted, takes the access it gave with it. A role set for them, and the tasks they watched, go too.
• Remove someone added by name and they keep access only if a unit or team gives it.

Every change is in the audit log: who gave or took away access, to whom, and how.

Roles

Role	Can
Project owner	Everything: the project's settings, columns, fields and access, roles, archiving; delete any task.
Member	Create, change and move tasks, plan and run sprints, comment.
Viewer	Read the board and tasks, comment and watch.

The person who creates a project is its owner. Owners make others owners (pick Project owner next to their name). Someone's role is the strongest their units give, unless a role was set for them; (from units) in the list puts them back to that.

[!NOTE] A project always keeps an active owner: the last one can't step down or be removed until someone else is an owner.

Desk admins manage every project, also those they aren't in, and appear as Desk admin there.