Repository roles for organizations
You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization by assigning them to roles. Choose the role that best fits each person or team's function in your project without giving people more access to the project than they need.
From least access to most access, the roles 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, discussions, 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
You can create custom repository roles. For more information, see "Managing custom repository roles for an organization."
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 access to every repository owned by the organization. For more information, see "Roles in 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.
Permissions for each role
Note: The roles required to use security features are listed in "Access requirements for security features" below.
Access requirements for security features
In this section, you can find the access required for security features, such as Advanced Security features.
|Receive Dependabot alerts for insecure dependencies in a repository|
|Dismiss Dependabot alerts|
|Designate additional people or teams to receive security alerts|
|Create security advisories|
|Manage access to GitHub Advanced Security features (see "Managing security and analysis settings for your organization")|
|Enable the dependency graph for a private repository|
|View dependency reviews|
|View code scanning alerts on pull requests|
|List, dismiss, and delete code scanning alerts|
|View and dismiss secret scanning alerts in a repository|
|Resolve, revoke, or re-open secret scanning alerts|
|Designate additional people or teams to receive secret scanning alerts in repositories|
Note: Repository writers and maintainers can only see secret scanning alert information for their own commits.