This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2020-11-12. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Repository permission levels for an organization

You can customize access to each repository in your organization with granular permission levels, giving people access to the features and tasks they need.

In this article

Did this doc help you?

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

Or, learn how to contribute.

People with admin permissions can manage individual and team access to an organization-owned repository.

Permission levels for repositories owned by an organization

You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization. Each permission level progressively increases access to a repository's content and settings. Choose the level that best fits each person or team's role in your project without giving people more access to the project than they need.

From least access to most access, the permission levels for an organization repository are:

  • Read: Recommended for non-code contributors who want to view or discuss your project
  • Triage: Recommended for contributors who need to proactively manage issues and pull requests without write access
  • Write: Recommended for contributors who actively push to your project
  • Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
  • Admin: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository

For more information about giving people and teams access to repositories, see "Managing access to your organization's repositories."

Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "Setting base permissions for an organization."

Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "Managing organization settings."

In addition to managing organization-level settings, organization owners have admin permissions for every repository owned by the organization. For more information, see "Permission levels for an organization."

Warning: When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization.

Repository access for each permission level

Repository actionReadTriageWriteMaintainAdmin
Pull from the person or team's assigned repositoriesXXXXX
Fork the person or team's assigned repositoriesXXXXX
Edit and delete their own commentsXXXXX
Open issuesXXXXX
Close issues they opened themselvesXXXXX
Reopen issues they closed themselvesXXXXX
Have an issue assigned to themXXXXX
Send pull requests from forks of the team's assigned repositoriesXXXXX
Submit reviews on pull requestsXXXXX
View published releasesXXXXX
Edit wikisXXXXX
Apply labelsXXXX
Close, reopen, and assign all issues and pull requestsXXXX
Apply milestonesXXXX
Mark duplicate issues and pull requestsXXXX
Request pull request reviewsXXXX
Push to (write) the person or team's assigned repositoriesXXX
Edit and delete anyone's comments on commits, pull requests, and issuesXXX
Hide anyone's commentsXXX
Lock conversationsXXX
Transfer issues (see "Transferring an issue to another repository" for details)XXX
Act as a designated code owner for a repositoryXXX
Mark a draft pull request as ready for reviewXXX
Submit reviews that affect a pull request's mergeabilityXXX
Apply suggested changes to pull requestsXXX
Create status checksXXX
Create and edit releasesXXX
View draft releasesXXX
Edit a repository's descriptionXX
Manage topicsXX
Enable wikis and restrict wiki editorsXX
Enable project boardsXX
Configure pull request mergesXX
Configure a publishing source for GitHub PagesXX
Push to protected branchesXX
Create and edit repository social cardsXX
Delete an issue (see "Deleting an issue")X
Merge pull requests on protected branches, even if there are no approving reviewsX
Define code owners for a repositoryX
Add a repository to a team (see "Managing team access to an organization repository" for details)X
Manage outside collaborator access to a repositoryX
Change a repository's visibilityX
Make a repository a template (see "Creating a template repository")X
Change a repository's settingsX
Manage team and collaborator access to the repositoryX
Edit the repository's default branchX
Manage webhooks and deploy keysX
Manage the forking policy for a repositoryX
Transfer repositories into the organizationX
Delete or transfer repositories out of the organizationX
Archive repositoriesX
Create autolink references to external resources, like JIRA or Zendesk (see "Configuring autolinks to reference external resources")X

Further reading

Did this doc help you?

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

Or, learn how to contribute.