Skip to main content



对仓库具有管理员权限的人员可以管理团队对仓库的访问权限。 团队维护员可以删除团队对仓库的访问权限。


  • 如果团队能够直接访问仓库,您可以更改其权限级别。 如果团队对仓库的访问权限继承自父团队,则您必须更改团队对仓库的访问权限。
  • 如果您添加或删除父团队的仓库访问权限,则其每个子团队也会获得或失去相应的仓库访问权限。 更多信息请参阅“关于团队”。


您可以在仓库设置中授予团队对仓库的访问权限,或更改团队对仓库的访问权限级别。 更多信息请参阅“管理有权访问仓库的团队和人员”。


您可以在仓库设置中删除团队对组织仓库的访问权限。 更多信息请参阅“管理有权访问仓库的团队和人员”。

如果团队可以直接访问仓库,您可以删除该团队对仓库的访问。 如果团队对仓库的访问权限继承自父团队,则必须删除父团队对仓库的访问权限才可删除其子团队的相应权限。


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