Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
0c2dff4a
Commit
0c2dff4a
authored
Jan 19, 2021
by
Melissa Ushakov
Committed by
Mike Jang
Jan 19, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
IP restrictions are added at the group level
parent
f1a4ee68
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/user/group/index.md
doc/user/group/index.md
+2
-2
No files found.
doc/user/group/index.md
View file @
0c2dff4a
...
...
@@ -645,9 +645,9 @@ more information.
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
underlying
subgroups, projects, issues, and so on
, by IP address. This can help ensure that
particular content doesn't leave the premises, while not blocking off access to
the entire instance.
the entire instance.
IP access restrictions can only be configured at the group level.
Add one or more allowed IP subnets using CIDR notation to the group settings and anyone
coming from a different IP address won't be able to access the restricted
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment