Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc/user
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-11-19 09:10:06 +0300
committerGitLab Bot <gitlab-bot@gitlab.com>2021-11-19 09:10:06 +0300
commit97c07a2d3aba5c8614a30c91f0545374a8d1ed5f (patch)
treeb25e4a61a607531ed691dfd63eab6ed563c43115 /doc/user
parent1947c080b33184b0204e302f36954c0fa55b9109 (diff)
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
-rw-r--r--doc/user/group/index.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/user/group/index.md b/doc/user/group/index.md
index f0e08301a1b..b9539644b51 100644
--- a/doc/user/group/index.md
+++ b/doc/user/group/index.md
@@ -563,6 +563,8 @@ You should consider these security implications before configuring IP address re
requests a new job or an update to a job's state, it is also not bound by
the IP restrictions. But when the running CI/CD job sends Git requests from a
restricted IP address, the IP restriction prevents code from being cloned.
+- **User dashboard activity**: Users may still see some events from the IP restricted groups and projects
+ on their dashboard. Activity may include push, merge, issue, or comment events.
To restrict group access by IP address: