Roles and permissions
A project’s team is its channel: whoever is in the channel can see the project’s items. What each person can do depends on their role in the project and in the organization.
Project admins#
Project admins run the project. They are:
- the person who turned the project on;
- people another project admin adds;
- org owners and admins who are members of the channel.
Project admins can do everything members can, and also:
- change the project’s settings: the key, features, types, workflows, board columns, fields and labels;
- start and complete sprints;
- create, release, edit, reopen, archive and restore releases;
- import items from CSV;
- delete any item;
- set what happens when a GitHub pull request merges;
- turn the project off, and back on.
Add or remove a project admin#
- Open the project’s Settings tab and go to People.
- Select Add admin and pick a member of the channel who isn’t a guest, or open an admin’s menu and choose Remove as admin.
A removed admin stays in the channel and keeps working on items. If you remove yourself, you can’t change the settings again unless another admin adds you back. Settings are changed on a computer or the web.
Members#
Every member of the channel who isn’t a guest can:
- create items, edit their fields, change their status and comment;
- plan sprints: create sprints and move items into them;
- put items in releases through their fix version;
- link items, convert subtasks, and move items to the projects of other channels they’re in;
- delete the items they reported;
- share saved views with the project;
- generate release notes;
- create initiatives, and see GitHub activity on items.
Guests#
Guests can join a channel to follow its work, with a smaller set of actions:
- They can read the project’s items and comment in their threads.
- They can create items. A guest’s new item starts in the workflow’s starting status, and guests can’t set its assignee, status, estimate, sprint or fix version.
- They can edit the title and description of items they reported, but not other fields.
- They don’t see GitHub activity.
- A key for an item they can’t see stays plain text in chat, with no card.
- They see only the initiatives linked to epics in their channels.
- They can save views for themselves, but can’t share them.
People outside the channel#
Org members who aren’t in a project’s channel don’t see its items. For a public channel:
- the project shows under Public channels in the Work hub’s Projects, with Join channel;
- a key for one of its items in chat shows a card with the title, the channel and Join. See Items in chat.
Projects in private channels stay hidden from people outside them.
When someone leaves the channel#
When a member leaves a project’s channel, or is removed from it:
- their open items in the project are unassigned;
- they stop watching its items;
- the remaining project admins get one notification listing the open items that need a new assignee.
On phones#
Phones have the everyday work: items, boards, the backlog, comments and notifications. Project settings, the workflow designer, bulk edit, reports and CSV import are on a computer or the web; on phones you can look at the settings but not change them.