Article version: Enterprise Server 2.14

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-07-12. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Project board permissions for an organization

Organization owners and people with project board admin permissions can customize who has read, write, and admin permissions to your organization’s project boards.

In this article:

Permissions overview

There are three levels of permissions to a project board for people and teams:

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:

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

You can change the project board's visibility from private to public and back again. For more information, see "Changing project board visibility."

Further reading

Ask a human

Can't find what you're looking for?

Contact us