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.

En este artículo

Permission levels for an organization

Organization members can have owner 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."

  • Members are the default role for everyone else.

Organization actionOwnersMembers
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
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
Delete all teamsX
Delete the organization account, including all repositoriesX
Create teams (see "Setting team creation permissions in your organization" for details)XX
See all organization members and teamsXX
@mention any visible teamXX
Can be made a team maintainerXX
Transfer repositoriesX
Manage an organization's SSH certificate authorities (see "Managing your organization's SSH certificate authorities" for details)X
Create project boards (see "Project board permissions for an 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 (for more information, see "Managing disruptive comments)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
Set a team profile picture in all teams (see "Setting your team's profile picture" for details)X
Move teams in an organization's hierarchyX
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

App GitHub managers

By default, only organization owners can manage the settings of App GitHubs owned by an organization. To allow additional users to manage App GitHubs owned by an organization, an owner can grant them App GitHub manager permissions.

When you designate a user as a App GitHub manager in your organization, you can grant them access to manage the settings of some or all App GitHubs 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. Un colaborador externo es una persona que tiene acceso a uno o más repositorios de la organización, pero no es explícitamente miembro de la organización, como ser, un consultor o empleado transitorio. Para obtener más información, consulta:

Further reading

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.