About access permissions on GitHub
To perform any actions on GitHub, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams.
Roles work differently for different types of accounts. For more information about accounts, see "Types of GitHub accounts."
A repository owned by a personal account has two permission levels: the repository owner and collaborators. For more information, see "Permission levels for a personal account repository."
Organization members can have owner or member roles. Owners have complete administrative access to your organization. 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:
- "Roles in an organization"
- "Project board permissions for an organization"
- "Repository roles for an organization"
- "About teams"
Enterprise owners have ultimate power over the enterprise account and can take every action in the enterprise account. 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. For more information, see "Roles in an enterprise."