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.
Repository-level roles give organization members, outside collaborators and teams of people varying levels of access to repositories. For more information, see "Repository roles for an organization."
Team-level roles are roles that give permissions to manage a team. You can give any individual member of a team the team maintainer role, which gives the member a number of administrative permissions over a team. For more information, see "Assigning the team maintainer role to a team member."
Organization-level roles are sets of permissions that can be assigned to individuals or teams to manage an organization and the organization's repositories, teams, and settings. For more information about all the roles available at the organization level, see "About organization roles."
You can assign individuals or teams to a variety of organization-level roles to control your members' access to your organization and its resources. For more details about the individual permissions included in each role, see "Permissions for organization roles."
Organization owners have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "Maintaining ownership continuity for your organization."
The default, non-administrative role for people in an organization is the organization member. By default, organization members have a number of permissions, including the ability to create repositories and project boards.
Note: The security manager role is in public beta and subject to change.
Security manager is an organization-level role that organization owners can assign to any team in an organization. When applied, it gives every member of the team permissions to manage security alerts and settings across your organization, as well as read permissions for all repositories in the organization.
If your organization has a security team, you can use the security manager role to give members of the team the least access they need to the organization. For more information, see "Managing security managers in your organization."
By default, only organization owners can manage the settings of GitHub Apps owned by an organization. To allow additional users to manage GitHub Apps owned by an organization, an owner can grant them GitHub App manager permissions.
When you designate a user as a GitHub App manager in your organization, you can grant them access to manage the settings of some or all GitHub Apps owned by the organization. For more information, see:
- "Adding GitHub App managers in your organization"
- "Removing GitHub App managers from your organization"
To keep your organization's data secure while allowing access to repositories, you can add outside collaborators. An outside collaborator is a person who has access to one or more organization repositories but is not explicitly a member of the organization, such as a consultant or temporary employee. For more information, see:
- "Adding outside collaborators to repositories in your organization"
- "Converting an organization member to an outside collaborator"
- "Removing an outside collaborator from an organization repository"
|Organization action||Owners||Members||Security managers|
|Invite people to join the organization||X|
|Edit and cancel invitations to join the organization||X|
|Remove members from the organization||X|
|Reinstate former members to the organization||X|
|Add and remove people from all teams||X|
|Promote organization members to team maintainer||X|
|Configure code review assignments (see "Managing code review assignment for your team")||X|
|Add collaborators to all repositories||X|
|Access the organization audit log||X|
|Edit the organization's profile page (see "About your organization's profile")||X|
|Delete all teams||X|
|Delete the organization account, including all repositories||X|
|Create teams (see "Setting team creation permissions in your organization")||X||X||X|
|See all organization members and teams||X||X||X|
|@mention any visible team||X||X||X|
|Can be made a team maintainer||X||X||X|
|Manage security and analysis settings (see "Managing security and analysis settings for your organization")||X||X|
|Manage an organization's SSH certificate authorities (see "Managing your organization's SSH certificate authorities")||X|
|Create project boards (see "Project board permissions for an organization")||X||X||X|
|View and post public team discussions to all teams (see "About team discussions")||X||X||X|
|View and post private team discussions to all teams (see "About team discussions")||X|
|Edit and delete team discussions in all teams (for more information, see "Managing disruptive comments)||X|
|Hide comments on commits, pull requests, and issues (see "Managing disruptive comments")||X||X||X|
|Disable team discussions for an organization (see "Disabling team discussions for your organization")||X|
|Set a team profile picture in all teams (see "Setting your team's profile picture")||X|
|Move teams in an organization's hierarchy||X|
|Pull (read) all repositories in the organization||X||X|
|Push (write) and clone (copy) all repositories in the organization||X|
|Convert organization members to outside collaborators||X|
|View people with access to an organization repository||X|
|Export a list of people with access to an organization repository||X|
|Manage default labels (see "Managing default labels for repositories in your organization")||X|
|Manage IP allow lists (see "Restricting network traffic to your enterprise with an IP allow list")||X|