diff options
| author | 🚄 Job van der Voort 🚀 <job@gitlab.com> | 2018-04-16 15:23:34 +0000 |
|---|---|---|
| committer | 🚄 Job van der Voort 🚀 <job@gitlab.com> | 2018-04-16 15:23:34 +0000 |
| commit | e5dbe4ca6056d81c402e5dd796a13dedab1b2210 (patch) | |
| tree | 287b4e331da2ddd631dd6fbb2fad138537895de2 /doc/user | |
| parent | 1309a2c96001a83dbf20b30a68eb7f03c881f992 (diff) | |
| download | gitlab-ce-e5dbe4ca6056d81c402e5dd796a13dedab1b2210.tar.gz | |
link to product handbook piece on permissions
Diffstat (limited to 'doc/user')
| -rw-r--r-- | doc/user/permissions.md | 11 |
1 files changed, 2 insertions, 9 deletions
diff --git a/doc/user/permissions.md b/doc/user/permissions.md index 131458b261b..a9ba2a51242 100644 --- a/doc/user/permissions.md +++ b/doc/user/permissions.md @@ -15,16 +15,9 @@ GitLab [administrators](../README.md#administrator-documentation) receive all pe To add or import a user, you can follow the [project members documentation](../user/project/members/index.md). -## Principles - -Use this section as guidance for using existing and developing new features. - -1. All admin-only features should be within admin area. Outside of the admin area an admin should behave as regular user with highest access role. -2. Guest role for private projects should be equal to no role for public or internal project. -2. Reporter role is created to give user a maximum access to a project or group but without ability to modify source code or any other business critical resources. -3. Developer role should receive as much permissions as possible except those that are either destructive (ex. remove project) or restricted on purpose by higher role. -4. Master or owner roles should not be necessary for a daily workflow. The purpose of those roles is to do initial setup and maintainance. +## Principles behind permissions +See our [product handbook on permissions](https://about.gitlab.com/handbook/product#permissions-in-gitlab) ## Project members permissions |