The Wayback Machine - https://web.archive.org/web/20220303011332/https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization
Skip to main content
Free, Pro, & Team
English
Sign up
 
Organizations
Free, Pro, & Team
English
Sign up

 

Managing security managers in your organization

In this article

You can give your security team the least access they need to your organization by assigning a team to the security manager role.

Organization owners can assign the security manager role.

Note: The security manager role is in public beta and subject to change. This feature is not available for organizations using legacy per-repository billing plans.

Security manager is an organization-level role that organization owners can assign to any team in an organization. When applied, it gives every member of the team permissions to manage security alerts and settings across your organization, as well as read permissions for all repositories in the organization.

Permissions for the security manager role

Members of a team with the security manager role have only the permissions required to effectively manage security for the organization.

  • Read access on all repositories in the organization, in addition to any existing repository access
  • Write access on all security alerts in the organization
  • The ability to configure security settings at the organization level
  • The ability to configure security settings at the repository level

Additional functionality, including a security overview for the organization, is available in organizations that use GitHub Enterprise Cloud with Advanced Security. For more information, see the GitHub Enterprise Cloud documentation.

If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. For more information, see "Managing team access to an organization repository and "Managing teams and people with access to your repository."

Manage repository access UI with security managers

Assigning the security manager role to a team in your organization

You can assign the security manager role to a maximum of 10 teams in your organization.

  1. In the top right corner of GitHub.com, click your profile photo, then click Your organizations. Your organizations in the profile menu

  2. Next to the organization, click Settings. The settings button

  3. In the "Security" section of the sidebar, click Code security and analysis.

  4. Under Security managers, search for and select the team to give the role. Each team you select will appear in a list below the search bar. Add security manager

Removing the security manager role from a team in your organization

Warning: Removing the security manager role from a team will remove the team's ability to manage security alerts and settings across the organization, but the team will retain read access to repositories that was granted when the role was assigned. You must remove any unwanted read access manually. For more information, see "Managing team access to an organization repository."

  1. In the top right corner of GitHub.com, click your profile photo, then click Your organizations. Your organizations in the profile menu

  2. Next to the organization, click Settings. The settings button

  3. In the "Security" section of the sidebar, click Code security and analysis.

  4. Under Security managers, to the right of the team you want to remove as security managers, click . Remove security managers