Commit 3c353b2b authored by Suzanne Selhorn's avatar Suzanne Selhorn

Updated task steps to match standards

Related to: https://gitlab.com/gitlab-org/technical-writing/-/issues/454
parent 1bb57e7f
...@@ -30,18 +30,19 @@ To protect, update, or unprotect an environment, you need to have at least the ...@@ -30,18 +30,19 @@ To protect, update, or unprotect an environment, you need to have at least the
To protect an environment: To protect an environment:
1. Navigate to your project's **Settings > CI/CD**. 1. On the top bar, select **Menu > Projects** and find your project.
1. Expand the **Protected environments** section. 1. On the left sidebar, select **Settings > CI/CD**.
1. From the **Environment** dropdown menu, select the environment you want to protect. 1. Expand **Protected environments**.
1. In the **Allowed to Deploy** dropdown menu, select the role, users, or groups you 1. From the **Environment** list, select the environment you want to protect.
1. In the **Allowed to deploy** list, select the role, users, or groups you
want to give deploy access to. Keep in mind that: want to give deploy access to. Keep in mind that:
- There are two roles to choose from: - There are two roles to choose from:
- **Maintainers**: Allows access to all maintainers in the project. - **Maintainers**: Allows access to all of the project's users with the Maintainer role.
- **Developers**: Allows access to all maintainers and all developers in the project. - **Developers**: Allows access to all of the project's users with the Maintainer and Developer role.
- You can only select groups that are already associated with the project. - You can select groups that are already associated with the project only.
- Only users that have at least the Developer role appear in - Users must have at least the Developer role to appear in
the **Allowed to Deploy** dropdown menu. the **Allowed to deploy** list.
1. Click the **Protect** button. 1. Select **Protect**.
The protected environment now appears in the list of protected environments. The protected environment now appears in the list of protected environments.
...@@ -134,10 +135,10 @@ appears in the dropdown menu for deployment-only access. ...@@ -134,10 +135,10 @@ appears in the dropdown menu for deployment-only access.
To add deployment-only access: To add deployment-only access:
1. Add a group with Reporter permissions. 1. Add a group with the Reporter role.
1. Add user(s) to the group. 1. Add users to the group.
1. Invite the group to be a project member. 1. Invite the group to be a project member.
1. Follow the steps outlined in [Protecting Environments](#protecting-environments). 1. Follow the steps in [Protecting Environments](#protecting-environments).
Note that deployment-only access is the only possible access level for groups with [Reporter permissions](../../user/permissions.md). Note that deployment-only access is the only possible access level for groups with [Reporter permissions](../../user/permissions.md).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment