summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2019-05-12 15:28:14 +0000
committerEvan Read <eread@gitlab.com>2019-05-12 15:28:14 +0000
commit168e93acc1288f445cd298b25e87a149595c4e4d (patch)
treedee588703bd8d581742307bcb013017251ffb896
parent888758a54ab781694e98e3e2349abde754ee529e (diff)
parent40893c88b09215f2fb1f22cad1a5eeef9d473a28 (diff)
downloadgitlab-ce-168e93acc1288f445cd298b25e87a149595c4e4d.tar.gz
Merge branch 'patch-31' into 'master'
fix typos in new_ci_build_permissions_model.md See merge request gitlab-org/gitlab-ce!28087
-rw-r--r--doc/user/project/new_ci_build_permissions_model.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/new_ci_build_permissions_model.md b/doc/user/project/new_ci_build_permissions_model.md
index 6c3fa5eb463..d36312c9b8d 100644
--- a/doc/user/project/new_ci_build_permissions_model.md
+++ b/doc/user/project/new_ci_build_permissions_model.md
@@ -44,14 +44,14 @@ It is important to note that we have a few types of users:
- **Administrators**: CI jobs created by Administrators will not have access
to all GitLab projects, but only to projects and container images of projects
- that the administrator is a member of.That means that if a project is either
+ that the administrator is a member of. That means that if a project is either
public or internal users have access anyway, but if a project is private, the
Administrator will have to be a member of it in order to have access to it
via another project's job.
- **External users**: CI jobs created by [external users](../permissions.md#external-users-permissions) will have
access only to projects to which user has at least reporter access. This
- rules out accessing all internal projects by default,
+ rules out accessing all internal projects by default.
This allows us to make the CI and permission system more trustworthy.
Let's consider the following scenario: