Permission levels for an organization

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

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."
Billing managers allow a person to manage billing settings. For more information, see "Adding a billing manager to your organization".
Members are the default role for everyone else.

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 action	Owners	Members	Billing managers
Create repositories (see "Restricting repository creation in your organization" for details)	X	X
View and edit billing information	X		X
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
Set scheduled reminders (see "Managing scheduled reminders for pull requests")	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" for details)	X
Verify the organization's domains (see "Verifying your organization's domain" for details)	X
Restrict email notifications to verified or approved domains (see "Restricting email notifications for your organization" for details)	X
Delete all teams	X
Delete the organization account, including all repositories	X
Create teams (see "Setting team creation permissions in your organization" for details)	X	X
Move teams in an organization's hierarchy	X
Create project boards (see "Project board permissions for an organization" for details)	X	X
See all organization members and teams	X	X
@mention any visible team	X	X
Can be made a team maintainer	X	X
View organization insights (see "Viewing insights for your organization" for details)	X	X
View and post public team discussions to all teams (see "About team discussions" for details)	X	X
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)	X	X
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
Sponsor accounts and manage the organization's sponsorships (see "Sponsoring open-source contributors" for details)	X	X
Manage email updates from sponsored accounts (see "Managing updates from accounts your organization's sponsors" for details)	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" 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-on	X
Manage a user's SAML access to your organization	X
Manage an organization's SSH certificate authorities (see "Managing your organization's SSH certificate authorities" for details)	X
Transfer repositories	X
Purchase, install, manage billing for, and cancel GitHub Marketplace apps	X
List apps in GitHub Marketplace	X
Receive Dependabot alerts about vulnerable dependencies for all of an organization's repositories	X
Manage Dependabot security updates (see "About Dependabot security updates")	X
Manage the forking policy	X
Limit activity in public repositories in an organization	X
Pull (read), 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 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
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'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:

Explore by product

Permission levels for an organization

In this article