docs/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md

title, intro, miniTocMaxHeadingLevel, redirect_from, versions

title	intro	miniTocMaxHeadingLevel	redirect_from	versions
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.	4	/articles/repository-permission-levels-for-an-organization-early-access-program/ /articles/repository-permission-levels-for-an-organization	free-pro-team enterprise-server github-ae * * *

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

{% if currentVersion == "free-pro-team@latest" %}

{% endif %}

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 %}

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.

{% endwarning %}

Repository access for each permission level

{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} {% note %}

Note: Repository permissions required to use security features are listed in "Permission requirements for security features" below.

{% endnote %} {% endif %}

Repository action	Read	Triage	Write	Maintain	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
View GitHub Actions workflow runs	X	X	X	X	X
Edit wikis	X	X	X	X	X
Report abusive or spammy content	X	X	X	X	X
Apply/dismiss labels		X	X	X	X
Create, edit, delete labels			X	X	X
Close, reopen, and assign all issues and pull requests		X	X	X	X
Enable and disable auto-merge on a pull request			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
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
Convert a pull request to a draft			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, edit, run, re-run, and cancel GitHub Actions workflows			X	X	X
Create and edit releases			X	X	X
View draft releases			X	X	X
Edit a repository's description				X	X
View and install packages	X	X	X	X	X
Publish packages			X	X	X
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Delete and restore packages{% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}Delete packages{% endif %}					X
Manage topics				X	X
Enable wikis and restrict wiki editors				X	X
Enable project boards				X	X
Configure pull request merges				X	X
Configure a publishing source for {% data variables.product.prodname_pages %}				X	X
Push to protected branches				X	X
Create and edit repository social cards				X	X
Limit interactions in 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 "Managing team access to an organization repository" 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
Rename the repository's default branch (see "Renaming a branch")					X
Rename a branch other than the repository's default branch (see "Renaming a branch")			X	X	X
Manage webhooks and deploy keys					X
Manage data use settings for your private repository					X
Manage the forking policy for a 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
Create autolink references to external resources, like JIRA or Zendesk (see "Configuring autolinks to reference external resources")					X
Enable {% data variables.product.prodname_discussions %} in a repository				X	X
Create and edit categories for {% data variables.product.prodname_discussions %}				X	X
Move a discussion to a different category			X	X	X
Transfer a discussion to a new repository			X	X	X
Manage pinned discussions			X	X	X
Convert issues to discussions in bulk			X	X	X
Lock and unlock discussions		X	X	X	X
Individually convert issues to discussions		X	X	X	X
Create new discussions and comment on existing discussions	X	X	X	X	X
Delete a discussion				X	X

{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}

Permission requirements for security features

In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_advanced_security %} features.

| Repository action | Read | Triage | Write | Maintain | Admin | |:---|:---:|:---:|:---:|:---:|:---:|{% if currentVersion == "free-pro-team@latest" %} | Receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in a repository | | | | | X | | Dismiss {% data variables.product.prodname_dependabot_alerts %} | | | | | X | | Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies | | | | | X | | Create security advisories | | | | | X |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} | Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "Managing security and analysis settings for your organization") | | | | | X |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | Enable the dependency graph for a private repository | | | | | X | | View dependency reviews | X | X | X | X | X |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} | View {% data variables.product.prodname_code_scanning %} alerts on pull requests | X | X | X | X | X | | List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts | | | X | X | X |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} | View {% data variables.product.prodname_secret_scanning %} alerts in a repository | | | | | X | | Resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts | | | | | X | | Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts in repositories | | | | | X |{% endif %} {% endif %}

Further reading

• "Managing access to your organization's repositories"
• "Adding outside collaborators to repositories in your organization"
• "Project board permissions for an organization"