Skip to main content

조직 리포지토리에 대한 개인 액세스 권한 관리

조직에서 소유한 리포지토리에 대한 사용자의 액세스를 관리할 수 있습니다.

이 기능을 사용할 수 있는 사용자

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.

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

Managing an individual's access to an organization repository

You can give a person access to a repository or change a person's level of access to a repository in your repository settings. For more information, see "Managing teams and people with access to your repository."

Further reading