Skip to main content

Managing team access to an organization project (classic)

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" 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.

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 top right corner of GitHub.com, click your profile photo, then click Your organizations. Your organizations in the profile menu

  2. Click the name of your organization. Organization name in list of organizations

  3. Under your organization name, click Projects.

    Projects tab for your organization

  4. Click Projects (classic)

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

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

  7. Click , then click Settings. Settings option in drop-down menu from project board sidebar

  8. In the left sidebar, click Teams.

  9. To add a team, click Add a team: Select team. Then, choose a team from the drop-down menu or search for the team you'd like to add. Add a team drop-down menu with list of teams in organization

  10. Next to the team name, use the drop-down menu to select the desired permission level: Read, Write, or Admin. Team permissions drop-down menu with read, write, and admin options

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 top right corner of GitHub.com, click your profile photo, then click Your organizations. Your organizations in the profile menu

  2. Click the name of your organization. Organization name in list of organizations

  3. Under your organization name, click Teams.

    Teams tab

  4. On the Teams tab, click the name of the team. List of the organization's teams

  5. Above the team's conversation, click Projects. The team repositories tab

  6. To change permissions levels, to the right of the classic project you want to update, use the drop-down. To remove a classic project, click . Remove a project board from your team trash button