Article version: GitHub.com

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.

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

In this article

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:

Note: The triage and maintain roles are currently in public beta and are subject to change. The new roles will be gradually rolled out to all organizations soon.

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

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 action Read Triage (beta) Write Maintain (beta) Admin
Pull from the person or team's assigned repositories X X X X X
Fork the person or team's assigned repositories X X X X X
Edit and delete their own comments X X X X X
Open issues X X X X X
Close issues they opened themselves X X X X X
Reopen issues they closed themselves X X X X X
Have an issue assigned to them X X X X X
Send pull requests from forks of the team's assigned repositories X X X X X
Submit reviews on pull requests X X X X X
View published releases X X X X X
Edit wikis X X X X X
Report abusive or spammy content X X X X X
Apply labels X X X X
Close, reopen, and assign all issues and pull requests X X X X
Apply milestones X X X X
Mark duplicate issues and pull requests X X X X
Request pull request reviews X X X X
Push to (write) the person or team's assigned repositories X X X
Edit and delete anyone's comments on commits, pull requests, and issues X X X
Hide anyone's comments X X X
Lock conversations X X X
Close, reopen, and assign all issues X X X
Transfer issues (see "Transferring an issue to another repository" for details) X X X
Act as a designated code owner for a repository X X X
Mark a draft pull request as ready for review X X X
Submit reviews that affect a pull request's mergeability X X X
Apply suggested changes to pull requests X X X
Create status checks X X X
Create and edit releases X X X
View draft releases X X X
Edit a repository's description X X
Manage topics X X
Enable wikis and restrict wiki editors X X
Enable project boards X X
Configuring pull request merges X X
Configuring a publishing source for GitHub GitHub Pages") X X
Push to protected branches X X
Create and edit repository social cards X X
Limit interactions with a repository X X
Delete an issue (see "Deleting an issue") X
Merge pull requests on protected branches, even if there are no approving reviews X
Define code owners for a repository X
Add a repository to a team (see "Adding a repository to a team" for details) X
Manage outside collaborator access to a repository X
Change a repository's visibility X
Make a repository a template (see "Creating a template repository") X
Change a repository's settings X
Manage team and collaborator access to the repository X
Edit the repository's default branch X
Manage webhooks, service hooks, and deploy keys X
Enable the dependency graph for a private repository X
Receive security alerts for vulnerable dependencies in a repository X
Designate additional people or teams to receive security alerts for vulnerable dependencies X
Opt in to data use for a private repository X
Create maintainer security advisories X
Allow or disable forks for a specific private repository X
Transfer repositories into the organization X
Delete or transfer repositories out of the organization X
Archive repositories X
Display a sponsor button (see "Displaying a sponsor button in your repository") X

Further reading

Ask a human

Can't find what you're looking for?

Contact us