summaryrefslogtreecommitdiff
path: root/doc/permissions
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axilleas@axilleas.me>2016-03-17 09:24:06 +0200
committerAchilleas Pipinellis <axilleas@axilleas.me>2016-03-17 09:24:06 +0200
commitcde7eee73e611ca7f775e179fb07b931c37f54ae (patch)
tree51e40bbc67f5529789d2e54b1010dc88b331497e /doc/permissions
parent59064aeeef8562a87d4d03efa9b11012a007e261 (diff)
downloadgitlab-ce-cde7eee73e611ca7f775e179fb07b931c37f54ae.tar.gz
Refactor external users docs
[ci skip]
Diffstat (limited to 'doc/permissions')
-rw-r--r--doc/permissions/permissions.md32
1 files changed, 18 insertions, 14 deletions
diff --git a/doc/permissions/permissions.md b/doc/permissions/permissions.md
index 2dfd08755ba..3d375e47c8e 100644
--- a/doc/permissions/permissions.md
+++ b/doc/permissions/permissions.md
@@ -74,17 +74,21 @@ Any user can remove themselves from a group, unless they are the last Owner of t
## External Users
-In cases where it is desired that a user has access to some internal or private projects, but others
-should remain hidden from this user, there is the option of creating `External Users`.
-An administrator can flag a user as external through the API or by checking the checkbox on the admin panel.
-
-In the case of a new user: navigate to the **Admin** area and click the **New User** button. If you would like to
-edit a user, go to the user list on the **Admin** area and click the **Edit** button.
-
-External users can only access projects to which they are explicitly granted access, thus hiding all internal projects.
-Access can be granted by adding the users as member to the project or by including this user in a group. External users will, like usual users, receive
-a role in the project or group with all the abilities that are mentioned in the table above.
-
-External users cannot create groups or projects, and have the same access as logged out users in all other cases. This feature may be
-useful when for example a contractor is working on a given project and should only access the given project and public
-projects.
+In cases where it is desired that a user has access only to some internal or
+private projects, there is the option of creating **External Users**. This
+feature may be useful when for example a contractor is working on a given
+project and should only have access to that project.
+
+External users can only access projects to which they are explicitly granted
+access, thus hiding all other internal or private ones from them. Access can be
+granted by adding the user as member to the project or group.
+
+They will, like usual users, receive a role in the project or group with all
+the abilities that are mentioned in the table above. They cannot however create
+groups or projects, and they have the same access as logged out users in all
+other cases.
+
+An administrator can flag a user as external [through the API](../api/users.md)
+or by checking the checkbox on the admin panel. As an administrator, navigate
+to **Admin > Users** to create a new user or edit an existing one. There, you
+will find the option to flag the user as external.