Article version:

Permission levels for an organization

After you create an organization, you should give Owner permissions to a small group of people who will manage the organization account.

In this article

Permission levels for an organization

Organization members can have owner, billing manager, or member roles:

Organization actionOwnersMembersBilling managers
Create repositories (see "Restricting repository creation in your organization" for details)XX
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" for details)X
Verify the organization's domains (see "Verifying your organization's domain" for details)X
Delete all teamsX
Delete the organization account, including all repositoriesX
Create teams (see "Setting team creation permissions in your organization" for details)XX
Move teams in an organization's hierarchyX
Create project boards (see "Project board permissions for an organization" for details)XX
See all organization members and teamsXX
@mention any visible teamXX
Can be made a team maintainerXX
View organization insights (see "Viewing insights for your organization" for details)XX
View and post public team discussions to all teams (see "About team discussions" for details)XX
View and post private team discussions to all teams (see "About team discussions" for details)X
Edit and delete team discussions in all teams (see "Managing disruptive comments" for details)X
Hide comments on commits, pull requests, and issues (see "Managing disruptive comments" for details)XX
Disable team discussions for an organization (see "Disabling team discussions for your organization" for details)X
Manage viewing of organization dependency insights (see "Changing the visibility of your organization's dependency insights" for details)X
Set a team profile picture in all teams (see "Setting your team's profile picture" for details)X
Manage security and analysis settings (see "Managing security and analysis settings for your organization" for details)X
Enable and enforce SAML single sign-onX
Manage a user's SAML access to your organizationX
Manage an organization's SSH certificate authorities (see "Managing your organization's SSH certificate authorities" for details)X
Transfer repositoriesX
Purchase, install, manage billing for, and cancel GitHub Marketplace appsX
List apps in GitHub MarketplaceX
Receive GitHub Dependabot alerts about vulnerable dependencies for all of an organization's repositoriesX
Manage GitHub Dependabot security updates (see "Configuring GitHub Dependabot security updates")X
Manage the forking policyX
Limit activity in public repositories in an organizationX
Pull (read), push (write), and clone (copy) all repositories in the organizationX
Convert organization members to outside collaboratorsX
View people with access to an organization repositoryX
Export a list of people with access to an organization repositoryX
Manage default labels (see "Managing default labels for repositories in your organization")X
Enable team synchronization (see "Managing team synchronization for your organization" for details)X

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 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:

Further reading

Ask a human

Can't find what you're looking for?

Contact us