summaryrefslogtreecommitdiff
path: root/doc/security
diff options
context:
space:
mode:
authorMatt Penna <mpenna@gitlab.com>2019-06-07 20:17:01 +0000
committerMattPennaThe3rd <mpenna@gitlab.com>2019-06-07 16:56:40 -0400
commitfc87880c96df615957aebe850f586bad9fba0044 (patch)
treec313e0220d494b8d27cbb8a0780a6fe56ee4a75c /doc/security
parentbe1d1c704311019ee415991a9eb785a056ff8931 (diff)
downloadgitlab-ce-fc87880c96df615957aebe850f586bad9fba0044.tar.gz
Added links to pertinent GitLab docs
Clarified who can push to a protected branch
Diffstat (limited to 'doc/security')
-rw-r--r--doc/security/information_exclusivity.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/security/information_exclusivity.md b/doc/security/information_exclusivity.md
index dc654c56d1c..2a0fb96cb8c 100644
--- a/doc/security/information_exclusivity.md
+++ b/doc/security/information_exclusivity.md
@@ -18,8 +18,9 @@ This is an inherent feature of a DVCS. All git management systems have this
limitation.
You can take steps to prevent unintentional sharing and information
-destruction. This is the reason why only certain people are allowed to invite
-others and why no user can force push a protected branch.
+destruction. This limitation is the reason why only certain people are allowed
+to [add users to a project](../user/project/members/) and why only a GitLab
+admin can [force push a protected branch](../project/protected_branches.html).
<!-- ## Troubleshooting