Organization owners and team maintainers can add repositories to a team, as well as change the team's read, write, and admin access to the repository.

Warnings:

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

Giving a team access to a repository

  1. In the top right corner of GitHub, click your profile photo, then click Your profile. Profile photo

  2. On the left side of your profile page, under "Organizations", click the icon for your organization. organization icons

  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 list of team members, click Repositories. The team repositories tab

  6. Above the list of repositories, click Add repository. The Add repository button

  7. In the "Search by repository name" field, type the name of a repository, then select it. Repository search field
  8. Optionally, to the right of the repository name, choose a different permission level for the team. Repository access level dropdown

Removing a team's access to a repository

You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams.

Warning:

  • If you remove a person’s access to a private repository, any of their forks of that private repository are deleted. Local clones of the private repository are retained. If a team's access to a private repository is revoked or a team with access to a private repository is deleted, and team members do not have access to the repository through another team, private forks of the repository will be deleted.

  • You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.

  • Organization owners can disable the ability to fork a specific private repository or to fork any private repository in an organization. For more information, see "Allowing people to fork a private repository owned by your organization" and "Allowing people to fork private repositories in your organization."

  1. In the top right corner of GitHub, click your profile photo, then click Your profile. Profile photo

  2. On the left side of your profile page, under "Organizations", click the icon for your organization. organization icons

  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 list of team members, click Repositories. The team repositories tab

  6. Select the repository or repositories you'd like to remove from the team. List of team repositories with the checkboxes for some repositories selected

  7. Above the list of repositories, use the drop-down menu, and click Remove from team. Drop-down menu with the option to remove a repository from a team
  8. Review the repository or repositories that will be removed from the team, then click Remove repositories. Modal box with a list of repositories that the team will no longer have access to