Roles in an 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 pre-defined organization roles

Pre-defined organization roles are roles that are available by default in every organization. You don't need to create them yourself. They can include both organization permissions that let the recipient manage the organization, as well as repository permissions that apply to all of the repositories in the organization. The following pre-defined roles are built into every organization based on common patterns of permissions organizations usually need.

The current set of pre-defined roles are:

• All-repository read: Grants read access to all repositories in the organization.
• All-repository write: Grants write access to all repositories in the organization.
• All-repository triage: Grants triage access to all repositories in the organization.
• All-repository maintain: Grants maintenance access to all repositories in the organization.
• All-repository admin: Grants admin access to all repositories in the organization.

For more information, see "Using organization roles."

About organization roles

You can assign people 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."

For more granular control of access to your organization's settings, you can create a custom organization role. For more information, see "About custom organization roles."

If your organization is owned by an enterprise account, enterprise owners can choose to join your organization with any role. For more information, see "Managing your role in an organization owned by your enterprise."

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

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

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 view security alerts and manage settings for code security 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 App registrations owned by an organization. To allow additional users to manage GitHub App registrations 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 App registrations owned by the organization. The GitHub App manager role does not grant users access to install and uninstall GitHub Apps on an organization. For more information, see "Adding and removing GitHub App managers in your organization."

Outside collaborators or repository 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.

If your enterprise uses managed user accounts, the outside collaborator role is called "repository collaborator." A repository collaborator must be part of your enterprise, with a managed user account provisioned from your identity provider. If the user does not already consume a license, the user will consume a license after you grant access to a repository. For more information, see "About per-user pricing."

Generally, the outside collaborator and repository collaborator roles are equivalent, and the documentation for outside collaborators also applies to repository collaborators. However, the following distinctions apply:

• You cannot enforce two-factor authentication (2FA) for repository collaborators, because this feature is not available with Enterprise Managed Users.
• Repository collaborators cannot bypass single sign-on (SSO) requirements, because SSO is managed at the enterprise level in an enterprise with managed users. However, like outside collaborators, they do not need to provide SSO authorization of credentials for organizations where they are a collaborator.
• Repository collaborators are subject to your enterprise IP allow list policy and your identity provider's conditional access policy. However, they are not subject to the organization's IP allow list policy.

Managing outside collaborators or repository collaborators

To manage access to repositories for outside collaborators or repository collaborators, 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"

To control who can add outside collaborators or repository collaborators to repositories, see:

• "Setting permissions for adding outside collaborators"
• "Enforcing repository management policies in your enterprise"

Permissions for organization roles

Further reading

• "Repository roles for an organization"