diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-11 00:08:26 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-11 00:08:26 +0300 |
| commit | 0e4f7fdbd5c9ce840eab21f558401c9048493621 (patch) | |
| tree | 13fd8fdd2446c82ee4aaf77d1a82f3b478be3f9a /doc/ci/environments | |
| parent | 83f0b8fcb5ddd5a4d0a0b7609db94276cd1f586b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/environments')
| -rw-r--r-- | doc/ci/environments/deployment_safety.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/environments/deployment_safety.md b/doc/ci/environments/deployment_safety.md index 317965dc290..033e499d3d0 100644 --- a/doc/ci/environments/deployment_safety.md +++ b/doc/ci/environments/deployment_safety.md @@ -25,8 +25,8 @@ If you are using a continuous deployment workflow and want to ensure that concur ## Restrict write access to a critical environment -By default, environments can be modified by any team member that has the -[Developer role or higher](../../user/permissions.md#project-members-permissions). +By default, environments can be modified by any team member that has at least the +[Developer role](../../user/permissions.md#project-members-permissions). If you want to restrict write access to a critical environment (for example a `production` environment), you can set up [protected environments](protected_environments.md). |