summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeremy Watson <jwatson@gitlab.com>2019-06-18 18:45:07 +0000
committerJeremy Watson <jwatson@gitlab.com>2019-06-18 18:45:07 +0000
commitdb2b8f6e8b69151966c84b468814360c96eb4f23 (patch)
treee79767165dd20b6774d013c1c2f5c0290a5c1bf3
parent2ffd71f8f1e7957ada82733b36a568ab316d60f2 (diff)
downloadgitlab-ce-docs-ip-access-restriction.tar.gz
Added IP restriction docs to groupsdocs-ip-access-restriction
-rw-r--r--doc/user/group/index.md19
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/user/group/index.md b/doc/user/group/index.md
index 97d309caf7c..d78b327e5fb 100644
--- a/doc/user/group/index.md
+++ b/doc/user/group/index.md
@@ -323,6 +323,25 @@ This will disable the option for all users who previously had permissions to
operate project memberships, so no new users can be added. Furthermore, any
request to add a new user to a project through API will not be possible.
+### IP access restriction **[ULTIMATE]**
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/1985) in
+[GitLab Ultimate](https://about.gitlab.com/pricing/) 12.0.
+
+To make sure only people from within your organization can access particular
+resources, you have the option to restrict access to groups and their
+underlying projects, issues, etc, by IP address. This can help ensure that
+particular content doesn't leave the premises, while not blocking off access to
+the entire instance.
+
+Add whitelisted IP subnet using CIDR notation to the group settings and anyone
+coming from a different IP address won't be able to access the restricted
+content.
+
+Restriction currently applies to UI, API access is not restricted.
+To avoid accidental lock-out, admins and group owners are are able to access
+the group regardless of the IP restriction.
+
#### Group file templates **[PREMIUM]**
Group file templates allow you to share a set of templates for common file