GitLab权限角色详解，摘自gitLab权限说明文档
GitLab权限简单总结
用户角色
| 角色 | 权限说明 |
|---|---|
| Guest | 可以创建issue、发表评论，不能读写版本库 |
| Reporter | 可以克隆代码，不能提交，QA、PM可以赋予这个权限 |
| Developer | 可以克隆代码、开发、提交、push，RD可以赋予这个权限 |
| Master | 可以创建项目、添加tag、保护分支、添加项目成员、编辑项目，核心RD负责人可以赋予这个权限 |
| Owner | 可以设置项目访问权限 - Visibility Level、删除项目、迁移项目、管理组成员，开发组leader可以赋予这个权限 |
组/项目的访问权限
| 类型 | 权限 说明 |
|---|---|
| Private | 只有组成员才能看到 |
| Internal | 只要登录的用户就能看到 |
| Public | 所有人都能看到 |
开源项目和组设置的是Internal
GitLab权限详细说明
Permissions
Users have different abilities depending on the access level they have in a particular group or project. If a user is both in a group's project and the project itself, the highest permission level is used.
On public and internal projects the Guest role is not enforced. All users will be able to create issues, leave comments, and clone or download the project code.
When a member leaves a team's project, all the assigned Issues and Merge Requests will be unassigned automatically.
GitLab administrators receive all permissions.
To add or import a user, you can follow the project members documentation.
For information on eligible approvers for Merge Requests, see Eligible approvers.
Principles behind permissions
See our product handbook on permissions
Instance-wide user permissions
By default, users can create top-level groups and change their usernames. A GitLab administrator can configure the GitLab instance to modify this behavior.
Project members permissions
NOTE: Note: In GitLab 11.0, the Master role was renamed to Maintainer.
The following table depicts the various user permission levels in a project.
| Action | Guest | Reporter | Developer | Maintainer | Owner |
|---|---|---|---|---|---|
| Download project | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| Leave comments | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| View Insights charts [ULTIMATE] | ✓ | ✓ | ✓ | ✓ | ✓ |
| View approved/blacklisted licenses [ULTIMATE] | ✓ | ✓ | ✓ | ✓ | ✓ |
| View license management reports [ULTIMATE] | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| View Security reports [ULTIMATE] | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| View project code | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| Pull project code | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| View GitLab Pages protected by access control | ✓ | ✓ | ✓ | ✓ | ✓ |
| View wiki pages | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| See a list of jobs | ✓ (3) | ✓ | ✓ | ✓ | ✓ |
| See a job log | ✓ (3) | ✓ | ✓ | ✓ | ✓ |
| Download and browse job artifacts | ✓ (3) | ✓ | ✓ | ✓ | ✓ |
| Create new issue | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| See related issues | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create confidential issue | ✓ (1) | ✓ | ✓ | ✓ | ✓ |
| View confidential issues | (2) | ✓ | ✓ | ✓ | ✓ |
| Assign issues | ✓ | ✓ | ✓ | ✓ | |
| Label issues | ✓ | ✓ | ✓ | ✓ | |
| Lock issue discussions | ✓ | ✓ | ✓ | ✓ | |
| Manage issue tracker | ✓ | ✓ | ✓ | ✓ | |
| Manage related issues [STARTER] | ✓ | ✓ | ✓ | ✓ | |
| Create issue from vulnerability [ULTIMATE] | ✓ | ✓ | ✓ | ✓ | |
| Manage labels | ✓ | ✓ | ✓ | ✓ | |
| Create code snippets | ✓ | ✓ | ✓ | ✓ | |
| See a commit status | ✓ | ✓ | ✓ | ✓ | |
| See a container registry | ✓ | ✓ | ✓ | ✓ | |
| See environments | ✓ | ✓ | ✓ | ✓ | |
| See a list of merge requests | ✓ | ✓ | ✓ | ✓ | |
| View project statistics | ✓ | ✓ | ✓ | ✓ | |
| View Error Tracking list | ✓ | ✓ | ✓ | ✓ | |
| Pull from Maven repository or NPM registry [PREMIUM] | ✓ | ✓ | ✓ | ✓ | |
| Publish to Maven repository or NPM registry [PREMIUM] | ✓ | ✓ | ✓ | ||
| Create new branches | ✓ | ✓ | ✓ | ||
| Push to non-protected branches | ✓ | ✓ | ✓ | ||
| Force push to non-protected branches | ✓ | ✓ | ✓ | ||
| Remove non-protected branches | ✓ | ✓ | ✓ | ||
| Create new merge request | ✓ | ✓ | ✓ | ||
| Assign merge requests | ✓ | ✓ | ✓ | ||
| Label merge requests | ✓ | ✓ | ✓ | ||
| Lock merge request discussions | ✓ | ✓ | ✓ | ||
| Manage/Accept merge requests | ✓ | ✓ | ✓ | ||
| Create new environments | ✓ | ✓ | ✓ | ||
| Stop environments | ✓ | ✓ | ✓ | ||
| Add tags | ✓ | ✓ | ✓ | ||
| Cancel and retry jobs | ✓ | ✓ | ✓ | ||
| Create or update commit status | ✓ | ✓ | ✓ | ||
| Update a container registry | ✓ | ✓ | ✓ | ||
| Remove a container registry image | ✓ | ✓ | ✓ | ||
| Create/edit/delete project milestones | ✓ | ✓ | ✓ | ||
| Use security dashboard [ULTIMATE] | ✓ | ✓ | ✓ | ||
| Dismiss vulnerability [ULTIMATE] | ✓ | ✓ | ✓ | ||
| Apply code change suggestions | ✓ | ✓ | ✓ | ||
| Create and edit wiki pages | ✓ | ✓ | ✓ | ||
| Use environment terminals | ✓ | ✓ | |||
| Run Web IDE's Interactive Web Terminals [ULTIMATE ONLY] | ✓ | ✓ | |||
| Add new team members | ✓ | ✓ | |||
| Enable/disable branch protection | ✓ | ✓ | |||
| Push to protected branches | ✓ | ✓ | |||
| Turn on/off protected branch push for devs | ✓ | ✓ | |||
| Enable/disable tag protections | ✓ | ✓ | |||
| Rewrite/remove Git tags | ✓ | ✓ | |||
| Edit project | ✓ | ✓ | |||
| Add deploy keys to project | ✓ | ✓ | |||
| Configure project hooks | ✓ | ✓ | |||
| Manage Runners | ✓ | ✓ | |||
| Manage job triggers | ✓ | ✓ | |||
| Manage variables | ✓ | ✓ | |||
| Manage GitLab Pages | ✓ | ✓ | |||
| Manage GitLab Pages domains and certificates | ✓ | ✓ | |||
| Remove GitLab Pages | ✓ | ✓ | |||
| Manage clusters | ✓ | ✓ | |||
| Manage license policy [ULTIMATE] | ✓ | ✓ | |||
| Edit comments (posted by any user) | ✓ | ✓ | |||
| Manage Error Tracking | ✓ | ✓ | |||
| Delete wiki pages | ✓ | ✓ | |||
| View project Audit Events | ✓ | ✓ | |||
| Switch visibility level | ✓ | ||||
| Transfer project to another namespace | ✓ | ||||
| Remove project | ✓ | ||||
| Delete issues | ✓ | ||||
| Force push to protected branches [^4] | |||||
| Remove protected branches [^4] |
- (1): All users are able to perform this action on public and internal projects, but not private projects.
- (2): Guest users can only view the confidential issues they created themselves
- (3): If Public pipelines is enabled in Project Settings > CI/CD
- (4): Not allowed for Guest, Reporter, Developer, Maintainer, or Owner
Project features permissions
Wiki and issues
Project features like wiki and issues can be hidden from users depending on which visibility level you select on project settings.
- Disabled: disabled for everyone
- Only team members: only team members will see even if your project is public or internal
- Everyone with access: everyone can see depending on your project visibility level
- Everyone: enabled for everyone (only available for GitLab Pages)
Protected branches
To prevent people from messing with history or pushing code without review, we've created protected branches. Read through the documentation on protected branches to learn more.
Additionally, you can allow or forbid users with Maintainer and/or Developer permissions to push to a protected branch. Read through the documentation on Allowed to Merge and Allowed to Push settings to learn more.
Cycle Analytics permissions
Find the current permissions on the Cycle Analytics dashboard on the documentation on Cycle Analytics permissions.
Issue Board permissions
Developers and users with higher permission level can use all the functionality of the Issue Board, that is create/delete lists and drag issues around. Read though the documentation on Issue Boards permissions to learn more.
File Locking permissions [PREMIUM]
The user that locks a file or directory is the only one that can edit and push their changes back to the repository where the locked objects are located.
Read through the documentation on permissions for File Locking to learn more.
Confidential Issues permissions
Confidential issues can be accessed by reporters and higher permission levels, as well as by guest users that create a confidential issue. To learn more, read through the documentation on permissions and access to confidential issues.
Releases permissions
Project Releases can be read by project members with Reporter, Developer, Maintainer, and Owner permissions. Guest users can access Release pages for downloading assets but are not allowed to download the source code nor see repository information such as tags and commits.
Releases can be created, updated, or deleted via Releases APIs by project Developers, Maintainers, and Owners.
Group members permissions
NOTE: Note: In GitLab 11.0, the Master role was renamed to Maintainer.
Any user can remove themselves from a group, unless they are the last Owner of the group. The following table depicts the various user permission levels in a group.
| Action | Guest | Reporter | Developer | Maintainer | Owner |
|---|---|---|---|---|---|
| Browse group | ✓ | ✓ | ✓ | ✓ | ✓ |
| View Insights charts [ULTIMATE] | ✓ | ✓ | ✓ | ✓ | ✓ |
| View group epic [ULTIMATE] | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create/edit group epic [ULTIMATE] | ✓ | ✓ | ✓ | ✓ | |
| Manage group labels | ✓ | ✓ | ✓ | ✓ | |
| Create project in group | ✓ | ✓ | ✓ | ||
| Create/edit/delete group milestones | ✓ | ✓ | ✓ | ||
| Enable/disable a dependency proxy [PREMIUM] | ✓ | ✓ | ✓ | ||
| Edit group | ✓ | ||||
| Create subgroup | ✓ | ||||
| Manage group members | ✓ | ||||
| Remove group | ✓ | ||||
| Delete group epic [ULTIMATE] | ✓ | ||||
| View group Audit Events | ✓ |
Subgroup permissions
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 have membership in one of its parents.
To learn more, read through the documentation on subgroups memberships.
External users permissions
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 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.
By default new users are not set as external users. This behavior can be changed by an administrator under Admin > Application Settings.
Default internal users
The "Internal users" field allows specifying an e-mail address regex pattern to identify default internal users.
New users whose email address matches the regex pattern will be set to internal by default rather than an external collaborator.
The regex pattern format is Ruby, but it needs to be convertible to JavaScript, and the ignore case flag will be set, e.g. "/regex pattern/i".
Here are some examples:
- Use
\.internal@domain\.com$to mark email addresses ending with ".internal@domain.com" internal. - Use
^(?:(?!\.ext@domain\.com).)*$\r?to mark users with email addresses NOT including .ext@domain.com internal.
Please be aware that this regex could lead to a DOS attack, see ReDos on Wikipedia.
Auditor users [PREMIUM ONLY]
Introduced in GitLab Premium 8.17.
Auditor users are given read-only access to all projects, groups, and other resources on the GitLab instance.
An Auditor user should be able to access all projects and groups of a GitLab instance with the permissions described on the documentation on auditor users permissions.
Read more about Auditor users.
Project features
Project features like wiki and issues can be hidden from users depending on which visibility level you select on project settings.
- Disabled: disabled for everyone
- Only team members: only team members will see even if your project is public or internal
- Everyone with access: everyone can see depending on your project visibility level
- Everyone: enabled for everyone (only available for GitLab Pages)
GitLab CI/CD permissions
NOTE: Note: In GitLab 11.0, the Master role was renamed to Maintainer.
GitLab CI/CD permissions rely on the role the user has in GitLab. There are four permission levels in total:
- admin
- maintainer
- developer
- guest/reporter
The admin user can perform any action on GitLab CI/CD in scope of the GitLab instance and project. In addition, all admins can use the admin interface under /admin/runners.
| Action | Guest, Reporter | Developer | Maintainer | Admin |
|---|---|---|---|---|
| See commits and jobs | ✓ | ✓ | ✓ | ✓ |
| Retry or cancel job | ✓ | ✓ | ✓ | |
| Erase job artifacts and trace | ✓ (1) | ✓ | ✓ | |
| Remove project | ✓ | ✓ | ||
| Create project | ✓ | ✓ | ||
| Change project configuration | ✓ | ✓ | ||
| Add specific runners | ✓ | ✓ | ||
| Add shared runners | ✓ | |||
| See events in the system | ✓ | |||
| Admin interface | ✓ |
- 1: Only if the job was triggered by the user
Job permissions
NOTE: Note: In GitLab 11.0, the Master role was renamed to Maintainer.
Note: GitLab 8.12 has a completely redesigned job permissions system. Read all about the new model and its implications.
This table shows granted privileges for jobs triggered by specific types of users:
| Action | Guest, Reporter | Developer | Maintainer | Admin |
|---|---|---|---|---|
| Run CI job | ✓ | ✓ | ✓ | |
| Clone source and LFS from current project | ✓ | ✓ | ✓ | |
| Clone source and LFS from public projects | ✓ | ✓ | ✓ | |
| Clone source and LFS from internal projects | ✓ (1) | ✓ (1) | ✓ | |
| Clone source and LFS from private projects | ✓ (2) | ✓ (2) | ✓ (2) | |
| Pull container images from current project | ✓ | ✓ | ✓ | |
| Pull container images from public projects | ✓ | ✓ | ✓ | |
| Pull container images from internal projects | ✓ (1) | ✓ (1) | ✓ | |
| Pull container images from private projects | ✓ (2) | ✓ (2) | ✓ (2) | |
| Push container images to current project | ✓ | ✓ | ✓ | |
| Push container images to other projects | ||||
| Push source and LFS |
- 1: Only if the user is not an external one
- 2: Only if the user is a member of the project
New CI job permissions model
GitLab 8.12 has a completely redesigned job permissions system. To learn more, read through the documentation on the new CI/CD permissions model.
Running pipelines on protected branches
The permission to merge or push to protected branches is used to define if a user can run CI/CD pipelines and execute actions on jobs that are related to those branches.
See Security on protected branches for details about the pipelines security model.
LDAP users permissions
Since GitLab 8.15, LDAP user permissions can now be manually overridden by an admin user. Read through the documentation on LDAP users permissions to learn more.
GitLab权限角色详解，摘自gitLab权限说明文档相关推荐
- pppd详解_pppd拨号脚本说明文档
// 加入调试信息 nodetach ipcp-accept-local ipcp-accept-remote usepeerdns // 使用服务器端协商的 DNS defaultroute // ...
- Gitlab搭建教程详解
Gitlab搭建教程详解 拟 制 人: 完成日期:2017-05-11 审 核 人: 审核日期: 修改记录 名称 版本号 拟制人/ 修改人 拟制/修改日期 更改理由 主要更改内容 (写要点即可) ...
- python权限管理系统_Django 自定义权限管理系统详解(通过中间件认证)
1. 创建工程文件, 修改setting.py文件 django-admin.py startproject project_name 特别是在 windows 上,如果报错,尝试用 django-a ...
- kubernetes（k8s）之rbac权限管理详解
kubernetes(k8s)之rbac权限管理详解 RBAC简介 RBAC(Role-Based Access Control) [外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传 ...
- Shiro权限管理详解（授权和注解开发）【面试点】
Shiro权限管理详解 1. 权限管理 1.1什么是权限管理 1.2用户身份认证 1.2.1 概念 1.2.2 用户名密码身份认证流程 1.2.3 关键对象 1.3 授权 1.3.1 概念 1.3.2 ...
- Windows权限设置详解
Windows权限设置详解 随着动网论坛的广泛应用和动网上传漏洞的被发现以及SQL注入式***越来越多的被使用,WEBSHELL让防火墙形同虚设,一台即使打了所有微软补丁.只让80端口对外开放的WEB ...
- Linux账号和权限管理详解（超详细示例操作）！
Linux账号和权限管理详解 一.用户账号和组账号概述 1.1 Linux基于用户身份对资源访问进行控制 1.2 用户账号 1.3 组账号 二.用户账号文件 2.1 用户账号文件 /etc/passw ...
- (转） shiro权限框架详解06-shiro与web项目整合(上)
http://blog.csdn.net/facekbook/article/details/54947730 shiro和web项目整合,实现类似真实项目的应用 本文中使用的项目架构是springM ...
- 19. linux中权限详解，Linux权限位，读写执行权限真正含义，chmod详解
linux中权限详解,Linux权限位,读写执行权限真正含义,chmod详解 文章目录 Linux权限位 读写执行 三种权限真正含义和作用 权限对文件的作用 权限对目录的作用 示例 chmod 使用数 ...
最新文章
- Google排名第一的技术，引数十万人关注！网友：差点我就放弃了！
- vuepress文档服务器,使用 vuepress 快速搭建文档
- javaScriptDay01
- JavaWeb课程复习资料——中文乱码上下文处理
- Java AIO初探(异步网络IO)
- 本文主要总结关于mysql的优化（将会持续更新）
- 从一个骗局谈生活中的基础算法
- 测开之路五十三：unittest运行参数
- 3.分布式服务架构：原理、设计与实战 --- 服务化系统容量评估和性能保障
- 双线性插值公式推导及Matlab实现
- mac无法验证您网络上的打印机，怎么解决？
- Freeswitch 怎么配置 Proxy Media 和 bypass 模式
- 扫盲区分IaaS和PaaS
- Python 玫瑰花绘制
- 扛过字节Java研发岗4轮面试，收到sp offer（月薪35k）！揭秘字节面试流程及考题(附带答案)
- Unity中实现使用Gizmo绘制出攻击范围
- 什么叫显示动力学，什么叫隐式动力学分析！
- 用matlab从rosbag文件里读取rbg图片和depth图片
- 「题解」300iq Contest 2 B Bitwise Xor
- P1100高低位交换