Skip to main content

This version of GitHub Enterprise was discontinued on 2023-01-18. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Managing an individual's access to an organization repository

You can manage a person's access to a repository owned by your organization.

Who can use this feature

People with admin access to a repository can manage access to the repository.

About access to organization repositories

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

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.

  • When LDAP Sync is enabled, if you remove a person from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync.

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

  • People with admin permissions to a private or internal repository can disallow forking of that repository, and organization owners can disallow forking of any private or internal repository in an organization. For more information, see "Managing the forking policy for your organization" and "Managing the forking policy for your repository."

Giving a person access to a repository

  1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.
  2. Under your repository name, click Settings. Repository settings button
  3. In the left sidebar, click Manage access. "Manage access" tab
  4. To the right of "Manage access", click Add people or Add teams. "Invite teams or people" button
  5. In the search field, start typing the name of the person to invite, then click a name in the list of matches. Search field for typing the name of a team or person to invite to the repository
  6. Under "Choose a role", select the repository role to assign the person, then click Add NAME to REPOSITORY. Selecting permissions for the team or person

Managing an individual's access to an organization repository

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

Further reading