About access permissions on GitHub
若要对 GitHub 执行任何操作，例如在存储库中创建拉取请求或更改组织的计费设置，用户必须具有对相关帐户或资源的足够访问权限。 此访问由权限控制。 权限是执行特定操作的能力。 例如，删除问题的能力是一种权限。 角色是你可以分配给个人或团队的一组权限。
Roles work differently for different types of accounts. For more information about accounts, see GitHub 帐户类型.
Personal accounts
A repository owned by a personal account has two permission levels: the repository owner and collaborators. See 个人帐户存储库的权限级别.
Organization accounts
Organization members can have owner, billing manager, or member roles. Owners have complete administrative access to your organization, while billing managers can manage billing settings. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
Enterprise accounts
Enterprise owners have ultimate power over the enterprise account and can take every action in the enterprise account. Billing managers can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings.
Enterprise owners cannot access organization content or repositories unless they are explicitly granted a role in the organization. However, enterprise owners can manage enterprise settings and policies that impact an organization in the enterprise. For more information, see 企业中的角色.
If an enterprise uses Enterprise Managed Users, members are provisioned as new personal accounts on GitHub and are fully managed by the identity provider. The 托管用户帐户 have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the 托管用户帐户 can be granted the same granular access levels available for regular organizations. For more information, see 关于 Enterprise Managed Users.
Next steps
Next, learn about how you can use rulesets to manage how people interact with your enterprise's repositories. See About rulesets.