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
1913f1ed
Commit
1913f1ed
authored
Mar 10, 2017
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add info on group membership
[ci skip]
parent
bb99fc25
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
29 additions
and
10 deletions
+29
-10
doc/user/group/subgroups/index.md
doc/user/group/subgroups/index.md
+29
-10
No files found.
doc/user/group/subgroups/index.md
View file @
1913f1ed
...
@@ -104,6 +104,9 @@ When you add a member to a subgroup, they inherit the membership and permission
...
@@ -104,6 +104,9 @@ When you add a member to a subgroup, they inherit the membership and permission
level from the parent group. This model allows access to nested groups if you
level from the parent group. This model allows access to nested groups if you
have membership in one of its parents.
have membership in one of its parents.
The group permissions for a member can be changed only by Owners and only on
the
**Members**
page of the group the member was added.
You can tell if a member has inherited the permissions from a parent group by
You can tell if a member has inherited the permissions from a parent group by
looking at the group's
**Members**
page.
looking at the group's
**Members**
page.
...
@@ -111,19 +114,35 @@ looking at the group's **Members** page.
...
@@ -111,19 +114,35 @@ looking at the group's **Members** page.
From the image above, we can deduct the following things:
From the image above, we can deduct the following things:
-
There are 5 members that have access to the group
**four**
-
There are 5 members that have access to the group
`four`
-
Administrator is the Owner and member of all subgroups
-
User0 is a Reporter and has inherited their permissions from group
`one`
-
User0 is a Reporter and has inherited their permissions from group
**one**
which is above the hierarchy of group
`four`
which is above the hierarchy of group
**four**
-
User1 is a Developer and has inherited their permissions from group
-
User1 is a Developer and has inherited their permissions from group
**one/two**
which is above the hierarchy of group
**four**
`one/two`
which is above the hierarchy of group
`four`
-
User2 is a Developer and has inherited their permissions from group
-
User2 is a Developer and has inherited their permissions from group
**one/two/three**
which is above the hierarchy of group
**four**
`one/two/three`
which is above the hierarchy of group
`four`
-
User3 is a Master of group
**four**
, there is no indication of a parent
-
For User3 there is no indication of a parent group, therefore they belong to
group therefore they belong to group
**four**
group
`four`
, the one we're inspecting
-
Administrator is the Owner and member of
**all**
subgroups and for that reason,
same as User3, there is no indication of an ancestor group
The group permissions for a member can be changed only by Owners and only on
### Overriding the ancestor group membership
the
**Members**
page of the group the member was added.
>**Note:**
You need to be an Owner of a group in order to be able to add members to it.
To override the membership of an ancestor group, simply add the user in the new
subgroup again, but with different permissions.
For example, if User0 was first added to group
`one/two`
with Developer
permissions, then they will inherit those permissions in every other subgroup
of
`one/two`
. To give them Master access to
`one/two/three`
, you would add them
again in that group as Master. Removing them from that group, the permissions
will fallback to those of the ancestor group.
Note that the higher permission wins, so if in the above example the permissions
where reversed, User0 would have Master access to all groups, even to the one
that was explicitly given Developer access.
## Mentioning subgroups
## Mentioning subgroups
...
...
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