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.