Permissions overview
There are three levels of permissions to a project board for people and teams:
- Read, which gives people permission to view a project board.
- Write, which gives people permission to view a project board, link repositories to a project board, and interact with a project board. For more information, see "Linking a repository to a project board."
- Admin, which gives people permission to view a project board, interact with a project board, manage project board settings, and manage other people's access to the project board.
Organization owners and people with admin permissions can give a person access to an organization project board individually, as an outside collaborator or organization member, or through their membership in a team or organization. An outside collaborator is someone who is not an organization member but given permissions to collaborate in your organization.
Organization owners and people with admin permissions to a project board can also:
- Set default project board permissions for all organization members.
- Manage access to the project board for organization members, teams, and outside collaborators. For more information, see "Managing team access to an organization project board", "Managing an individual’s access to an organization project board", or "Managing access to a project board for organization members."
- Manage project board visibility. For more information, see "Managing access to a project board for organization members."
Cascading permissions for project boards
If a person has multiple avenues of access to an organization project board (individually, through a team, or as an organization member), the highest project board permission level overrides lower permission levels.
For example, if an organization owner has given all organization members read permissions to a project board, and a project board admin gives an organization member write permissions to that board as an individual collaborator, that person would have write permissions to the project board.
Project board visibility
Organization owners can control the ability of organization members to create public project boards, or change the visibility of existing project boards to public. For more information, see "Allowing project visibility changes in your organization."
By default, user-owned and organization-wide project boards are private and only visible to people with read, write, or admin permissions to the project board. A public project board is visible to anyone with the project board's URL. Repository-level project boards share the visibility of their repository. That is, a private repository will have a private project, and this visibility cannot be changed. You can change the project board's visibility from private to public and back again. For more information, see "Changing project board visibility."