Organization owners can manage any person's access to a repository, as well as other relevant information about the person's relationship to the organization.

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.

  1. In the top right corner of GitHub Enterprise, 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 People. The People tab

  4. Click either Members or Outside collaborators to manage people with different types of access. Button to invite members or outside collaborators to an organization

  5. To the right of the name of the person you'd like to manage, use the drop-down menu, and click Manage access. The manage access link

  6. On the "Manage access" page, next to the repository, click Manage access. Manage access button for a repository

  7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership. Repository access matrix for the user

Removing access to private repositories

When you remove a collaborator from a repository in your organization, they lose read/write access to your repository. If the person has forked a private repository, then their fork is also deleted, but the person will still retain any local clones of your repository.