Skip to content

Commit abef502

Browse files
committed
added reusables, feature flag and other updates
1 parent fb1abe7 commit abef502

7 files changed

Lines changed: 36 additions & 36 deletions

File tree

content/code-security/getting-started/securing-your-organization.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,7 @@ Some security features are only available {% ifversion fpt %}for public reposito
2222

2323
## Managing access to your organization
2424

25-
You can use roles to control what actions people can take in your organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
26-
27-
{% ifversion fpt or ghes > 3.2 or ghae-issue-4999 %}
28-
You can assign the security manager role to security teams in your organization to give them security management permissions exclusively, without extra permissions that they do not require. For more information, see "[Managing the security manager role in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-the-security-manager-role-in-your-organization)."
29-
{% endif %}
25+
You can use roles to control what actions people can take in your organization. {% if security-managers %}For example, you can assign the security manager role to a team to give them the ability to manage security settings across your organization, as well as read access to all repositories.{% endif %} For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
3026

3127
{% ifversion fpt or ghes > 3.0 or ghae-next %}
3228

content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ children:
1818
- /giving-team-maintainer-permissions-to-an-organization-member
1919
- /adding-a-billing-manager-to-your-organization
2020
- /removing-a-billing-manager-from-your-organization
21-
- /managing-the-security-manager-role-in-your-organization
21+
- /managing-security-managers-in-your-organization
2222
shortTitle: Manage access with roles
2323
---
2424

content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-the-security-manager-role-in-your-organization.md renamed to content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md

Lines changed: 8 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,33 @@
11
---
2-
title: Managing the security manager role in your organization
2+
title: Managing security managers in your organization
33
intro: 'You can give your security team the least access they need to your organization by assigning a team to the security manager role.'
44
versions:
5-
fpt: '*'
6-
ghes: '>=3.3'
7-
ghae: 'issue-4999'
5+
feature: 'security-managers'
86
topics:
97
- Organizations
108
- Teams
119
shortTitle: Security manager role
1210
permissions: Organization owners can assign the security manager role.
1311
---
1412

15-
{% note %}
13+
{% data reusables.organizations.security-manager-beta-note %}
1614

17-
**Note:** The security manager role is in public beta and subject to change.
18-
19-
{% endnote %}
20-
21-
Organization owners can grant a team the permissions they need to manage security alerts and settings across your organization, as well as read access on all organization repositories, by assigning the security manager role.
15+
{% data reusables.organizations.about-security-managers %}
2216

2317
## Permissions for the security manager role
2418

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

27-
- Read access on all repositories in the organization, in addition to any existing repository access
21+
- Read access on all repositories in the organization, in addition to any existing repository access
2822
- Write access on all security alerts in the organization
2923
- Access to the organization's security overview
3024
- The ability to configure security settings at the organization level, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}
3125
- The ability to configure security settings at the repository level, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}
3226

33-
While a team will be granted read permission on all organization repositories upon being added as security managers, any existing repository permissions that the team had will stay the same. If a team has the security manager role, only organization owners will be able to change team access to repositories in the **Repositories** tab.
27+
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)."
3428

35-
Repository owners will be able to see if a security manager team has access to their repository in the **Manage access** tab in their repository settings. Under **Manage direct access**, any security manager teams will appear as **Managed by organization owners** and their permissions cannot be removed or edited by the repository owner.
29+
![Manage repository access disabled with security managers](/assets/images/help/organizations/repo-access-security-managers.png)
3630

37-
![Manage repository access with security managers](/assets/images/help/organizations/repo-access-security-managers.png)
3831
## Assigning the security manager role to a team in your organization
3932

4033
{% data reusables.profile.access_org %}
@@ -44,12 +37,11 @@ Repository owners will be able to see if a security manager team has access to t
4437
![Add security manager](/assets/images/help/organizations/add-security-managers.png)
4538
## Removing the security manager role from a team in your organization
4639

47-
4840
{% warning %}
4941

5042
**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](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#removing-a-teams-access-to-a-repository)."
5143

52-
{% end warning %}
44+
{% endwarning %}
5345

5446
{% data reusables.profile.access_org %}
5547
{% data reusables.profile.org_settings %}

content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -18,36 +18,35 @@ shortTitle: Roles in an organization
1818
## About roles
1919
{% data reusables.organizations.about-roles %}
2020

21-
You can give organization members, outside collaborators and teams of people varying levels of access to repositories by assigning repository roles. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
21+
Repository-level roles give organization members, outside collaborators and teams of people varying levels of access to repositories. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
2222

2323
Team-level roles are roles that give permissions to manage a team. You can give any individual member of a team the team maintainer role, which gives the member a number of administrative permissions over a team. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)."
2424

25-
Organization-level roles are different sets of permissions that can be assigned to individuals or teams to manage an organization and the repositories, teams and settings within it. For more information on each organization-level role, see [Roles for an organization](#roles-for-an-organization).
25+
Organization-level roles are sets of permissions that can be assigned to individuals or teams to manage an organization and the organization's repositories, teams, and settings. For more information about all the roles available at the organization level, see "[About organization roles](#about-organization-roles)."
26+
27+
## About organization roles
28+
29+
You can assign individuals or teams to a variety of organization-level roles to control your members' access to your organization and its resources. For more details about the individual permissions included in each role, see "[Permissions for organization roles](#permissions-for-organization-roles)."
2630

27-
## Roles for an organization
2831
### Organization owners
2932
Organization owners have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
3033

3134
### Organization members
32-
The default, non-administrative role for people in an organization is the organization member. Organization members have a number of permissions, including being able to create repositories and project boards.
35+
The default, non-administrative role for people in an organization is the organization member. By default, organization members have a number of permissions, including the ability to create repositories and project boards.
3336

3437
{% ifversion fpt %}
3538
### Billing managers
3639
Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
3740
{% endif %}
3841

39-
{% ifversion fpt or ghes > 3.2 or ghae-issue-4999 %}
42+
{% if security-managers %}
4043
### Security managers
4144

42-
{% note %}
43-
44-
**Note:** The security manager role is in public beta and subject to change.
45-
46-
{% endnote %}
45+
{% data reusables.organizations.security-manager-beta-note %}
4746

48-
Security manager is an organization-level role that can be assigned 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.
47+
{% data reusables.organizations.about-security-managers %}
4948

50-
If your organization has a security team, you can use the security manager role to give members of that team the permissions they need to do their job without any extra permissions they do not require. For more information, see "[Managing the security manager role in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-the-security-manager-role-in-your-organization)."
49+
If your organization has a security team, you can use the security manager role to give members of the team the least access they need to the organization. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)."
5150
{% endif %}
5251
### {% data variables.product.prodname_github_app %} managers
5352
By default, only organization owners can manage the settings of {% data variables.product.prodname_github_apps %} owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_apps %} owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions.
@@ -128,8 +127,9 @@ Some of the features listed below are limited to organizations using {% data var
128127
| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** | | | |
129128

130129
{% elsif ghes > 3.2 or ghae-issue-4999 %}
130+
<!--GHES 3.3+ and eventual GHAE release don't have the extra column for Billing managers, but have security managers-->
131131

132-
| Organization action test | Owners | Members | Security managers |
132+
| Organization action | Owners | Members | Security managers |
133133
|:--------------------|:------:|:-------:|:-------:|
134134
| Invite people to join the organization | **X** | | |
135135
| Edit and cancel invitations to join the organization | **X** | | |
@@ -172,7 +172,7 @@ Some of the features listed below are limited to organizations using {% data var
172172

173173

174174
{% else %}
175-
<!--GHE version doesn't have the extra column for Billing managers-->
175+
<!--GHES and GHAE older versions don't have the extra column for Billing managers or Security managers-->
176176

177177
| Organization action | Owners | Members |
178178
|:--------------------|:------:|:-------:|
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# Reference: #4999.
2+
# Documentation for the security manager org-level role
3+
versions:
4+
fpt: '*'
5+
ghes: '>=3.3'
6+
ghae: 'issue-4999'
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +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.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{% note %}
2+
3+
**Note:** The security manager role is in public beta and subject to change.
4+
5+
{% endnote %}

0 commit comments

Comments
 (0)