jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-30 03:01:36 -05:00
Code Issues Projects Releases Wiki Activity

updates based on feedback

Browse Source
This commit is contained in:
Sarita Iyer
2021-10-13 16:12:00 -04:00
parent 8dc45419d9
commit 28851849f6
3 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
assets/images/help/organizations/repo-access-security-managers.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 299 KiB

After

Width:  |  Height:  |  Size: 308 KiB

5
content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
View File

@@ -26,11 +26,12 @@ Members of a team with the security manager role have only the permissions requi
- The ability to configure security settings at the organization level, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}
- The ability to configure security settings at the repository level, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}
If a team has the security manager role, only organization owners can change the team's access to individual repositories. People with admin access to a repository can see the team's access in the repository's settings but cannot remove or change the access. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
If a team has the security manager role, people with admin access to the team can change the team's level of access to individual repositories but cannot remove the access to any repositories. Similarly, people with admin access to a repository can view and change the team's access in the repository's settings but cannot remove the access. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
![Manage repository access disabled with security managers](/assets/images/help/organizations/repo-access-security-managers.png)
![Manage repository access UI with security managers](/assets/images/help/organizations/repo-access-security-managers.png)
## 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.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}

2
data/reusables/organizations/about-security-managers.md
View File

@@ -1 +1 @@
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.
Security manager is an organization-level role that organization owners can assign to any team in an organization. When applied, it gives every direct 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.