Notes:
- Projects, the all-new projects experience, is now available. For more information about Projects, see "About Projects" and for information about migrating your classic project, see "Migrating from projects (classic)."
- You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a project board instead.
Note: If a person has multiple avenues of access to an organization classic project (individually, through a team, or as an organization member), the highest classic project permission level overrides lower permission levels. For more information, see "Project (classic) permissions for an organization."
Giving an organization member access to a classic project
-
In the top right corner of GitHub.com, click your profile photo, then click Your organizations.
-
Click the name of your organization.
-
Under your organization name, click Projects.
-
Click Projects (classic)
-
In the projects list, click the name of the classic project.
-
On the top-right side of the classic project, click Menu.
-
Click , then click Settings.
-
In the left sidebar, click Collaborators.
-
Under "Search by username, full name or email address", type the collaborator's name, username, or GitHub email.
-
In the search results, click the correct username and click Add collaborator.
-
Optionally, next to the new collaborator's name, use the drop-down menu and click the desired permission level: Read, Write, or Admin.
Changing an organization member's access to a classic project
-
In the top right corner of GitHub.com, click your profile photo, then click Your organizations.
-
Click the name of your organization.
-
Under your organization name, click Projects.
-
Click Projects (classic)
-
In the projects list, click the name of the classic project.
-
On the top-right side of the classic project, click Menu.
-
Click , then click Settings.
-
In the left sidebar, click Collaborators.
-
Optionally, next to the new collaborator's name, use the drop-down menu and click the desired permission level: Read, Write, or Admin.
Removing an organization member's access to a classic project
When you remove a collaborator from a classic project, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a classic project, you must remove access for each role the person has. For instance, a person may have access to the classic project as an organization member or team member. For more information, see "Project (classic) permissions for an organization."
-
In the top right corner of GitHub.com, click your profile photo, then click Your organizations.
-
Click the name of your organization.
-
Under your organization name, click Projects.
-
Click Projects (classic)
-
In the projects list, click the name of the classic project.
-
On the top-right side of the classic project, click Menu.
-
Click , then click Settings.
-
In the left sidebar, click Collaborators.
-
Next to the collaborator you want to remove, click X.
