Article version: Enterprise Server 2.17
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.
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 action | Owners | Members |
|---|---|---|
| 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 | |
| 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 | |
| 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 |
| See all organization members and teams | X | X |
| @mention any visible team | X | X |
| Can be made a team maintainer | X | X |
| Transfer repositories | X | |
| Create project boards (see "Project board permissions for an 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 (for more information, see "Managing disruptive comments | 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 | |
| Set a team profile picture in all teams (see "Setting your team's profile picture" for details) | X | |
| Move teams in an organization's hierarchy | 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 |
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:
- "Adding GitHub App managers in your organization"
- "Removing GitHub App managers from your organization"
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:
- "Adding outside collaborators to repositories in your organization"
- "Converting an organization member to an outside collaborator"
- "Removing an outside collaborator from an organization repository"