@@ -39,12 +39,13 @@ usernames. A GitLab administrator can configure the GitLab instance to
...
@@ -39,12 +39,13 @@ usernames. A GitLab administrator can configure the GitLab instance to
NOTE:
NOTE:
In GitLab 11.0, the Master role was renamed to Maintainer.
In GitLab 11.0, the Master role was renamed to Maintainer.
While Maintainer is the highest project-level role, some actions can only be performed by a personal namespace or group owner,
The Owner permission is only available at the group or personal namespace level (and for instance administrators) and is inherited by its projects.
or an instance administrator, who receives all permissions. For more information, see [projects members documentation](project/members/index.md).
While Maintainer is the highest project-level role, some actions can only be performed by a personal namespace or group owner, or an instance administrator, who receives all permissions.
For more information, see [projects members documentation](project/members/index.md).
The following table depicts the various user permission levels in a project.
The following table depicts the various user permission levels in a project.
@@ -201,7 +202,6 @@ The following table depicts the various user permission levels in a project.
...
@@ -201,7 +202,6 @@ The following table depicts the various user permission levels in a project.
1. When [Share Group Lock](group/index.md#prevent-a-project-from-being-shared-with-groups) is enabled the project can't be shared with other groups. It does not affect group with group sharing.
1. When [Share Group Lock](group/index.md#prevent-a-project-from-being-shared-with-groups) is enabled the project can't be shared with other groups. It does not affect group with group sharing.
1. For information on eligible approvers for merge requests, see
1. For information on eligible approvers for merge requests, see