Managing team access to an organization project (classic)

In this article

As an organization owner or classic project admin, you can give a team access to a classic project owned by your organization.

Notes:

  • Projects, the all-new projects experience, is now available. For more information about Projects, see "About Projects."
  • You can only create a new classic project board for an organization, repository, or user that already has at least one classic project board. If you're unable to create a classic project board, create a project instead.

Warnings:

  • You can change a team's permission level if the team has direct access to a classic project. If the team's access to the classic project is inherited from a parent team, you must change the parent team's access to the classic project.
  • If you add or remove classic project access for a parent team, each of that parent's child teams will also receive or lose access to the classic project. For more information, see "About teams."

Giving a team access to a classic project

You can give an entire team the same permission level to a classic project.

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 example, if an organization owner has given a team read permissions to a classic project, and a classic project admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the classic project. For more information see, "Project (classic) permissions for an organization."

  1. In the upper-right corner of GitHub Enterprise Server, select your profile photo, then click Your organizations.

    Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

  2. Click the name of your organization.

  3. Under your organization name, click Projects.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with a table icon and "Projects," is outlined in dark orange.

  4. Click Projects (classic)

  5. In the projects list, click the name of the classic project.

  6. On the top-right side of the classic project, click Menu.

  7. Click , then click Settings.

    Screenshot showing the project menu. The settings option is highlighted with an orange outline.

  8. In the left sidebar, click Teams.

  9. To add a team, click Add a team: Select team. Then, choose a team from the dropdown menu or search for the team you'd like to add.

  10. Next to the team name, use the dropdown menu to select the desired permission level: Read, Write, or Admin.

Configuring a team's access to a classic project

If a team's access to a classic project is inherited from a parent team, you must change the parent team's access to the classic project to update access to the child teams.

  1. In the upper-right corner of GitHub Enterprise Server, select your profile photo, then click Your organizations.

    Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

  2. Click the name of your organization.

  3. Under your organization name, click Teams.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with the people icon and "Teams," is outlined in dark orange.

  4. Click the name of the team.

  5. Above the team's conversation, click Projects.

    Screenshot of the main page for a team. In the horizontal navigation bar, the "Projects" tab is outlined in dark orange.

  6. To change permissions levels, to the right of the classic project you want to update, use the permission level dropdown menu.

Further reading