Skip to main content

Roles in an organization

Organization owners can assign roles to individuals and teams giving them different sets of permissions in the organization.

About roles

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

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

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

Organization members

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.

Organization moderators

Moderators are organization members who, in addition to their permissions as members, are allowed to block and unblock non-member contributors, set interaction limits, and hide comments in public repositories owned by the organization. For more information, see "Managing moderators in your organization."

Billing managers

Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. For more information, see "Adding a billing manager to your organization."

Security managers

Note: The security manager role is in public beta and subject to change. This feature is not available for organizations using legacy per-repository billing plans.

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

GitHub App managers

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:

Outside collaborators

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:

Permissions for organization roles

Some of the features listed below are limited to organizations using GitHub Enterprise Cloud. For more information about how you can try GitHub Enterprise Cloud for free, see "Setting up a trial of GitHub Enterprise Cloud."

Organization permissionOwnersMembersModeratorsBilling managersSecurity managers
Create repositories (see "Restricting repository creation in your organization")XXXX
View and edit billing informationXX
Invite people to join the organizationX
Edit and cancel invitations to join the organizationX
Remove members from the organizationX
Reinstate former members to the organizationX
Add and remove people from all teamsX
Promote organization members to team maintainerX
Configure code review assignments (see "Managing code review assignment for your team")X
Set scheduled reminders (see "Managing scheduled reminders for pull requests")X
Add collaborators to all repositoriesX
Access the organization audit logX
Edit the organization's profile page (see "About your organization's profile")X
Delete all teamsX
Delete the organization account, including all repositoriesX
Create teams (see "Setting team creation permissions in your organization")XXXX
Move teams in an organization's hierarchyX
Create project boards (see "Project board permissions for an organization")XXXX
See all organization members and teamsXXXX
@mention any visible teamXXXX
Can be made a team maintainerXXXX
View and post public team discussions to all teams (see "About team discussions")XXXX
View and post private team discussions to all teams (see "About team discussions")X
Edit and delete team discussions in all teams (see "Managing disruptive comments")X
Disable team discussions for an organization (see "Disabling team discussions for your organization")X
Hide comments on writable commits, pull requests, and issues (see "Managing disruptive comments")XXXX
Hide comments on all commits, pull requests, and issues (see "Managing disruptive comments")XXX
Block and unblock non-member contributors (see "Blocking a user from your organization")XX
Limit interactions for certain users in public repositories (see "Limiting interactions in your organization")XX
Set a team profile picture in all teams (see "Setting your team's profile picture")X
Sponsor accounts and manage the organization's sponsorships (see "Sponsoring open-source contributors")XXX
Manage email updates from sponsored accounts (see "Managing updates from accounts your organization's sponsors")X
Attribute your sponsorships to another organization (see "Attributing sponsorships to your organization" for details )X
Manage the publication of GitHub Pages sites from repositories in the organization (see "Managing the publication of GitHub Pages sites for your organization")X
Manage security and analysis settings (see "Managing security and analysis settings for your organization")XX
View the security overview for the organization (see "About the security overview")XX
Transfer repositoriesX
Purchase, install, manage billing for, and cancel GitHub Marketplace appsX
List apps in GitHub MarketplaceX
Receive Dependabot alerts about insecure dependencies for all of an organization's repositoriesXX
Manage Dependabot security updates (see "About Dependabot security updates")XX
Manage the forking policyX
Limit activity in public repositories in an organizationX
Pull (read) all repositories in the organizationXX
Push (write) and clone (copy) all repositories in the organizationX
Convert organization members to outside collaboratorsX
View people with access to an organization repositoryX
Manage the default branch name (see "Managing the default branch name for repositories in your organization")X
Manage default labels (see "Managing default labels for repositories in your organization")X
Manage pull request reviews in the organization (see "Managing pull request reviews in your organization")X

Further reading