As a fully functional project management system, GitLab manages its own set of access controls in addition to general access provided for by the Cascade SSO credential.
In GitLab, you use groups to manage one or more related projects at the same time. If someone has access to the group, here are some of the permissions they inherit:
- Access to all the projects in the group.
- View all of the issues and merge requests for the projects in the group.
- View analytics that show the group’s activity.
- Communicate with all of the members of the group at once.
Read more about managing groups and group features at: https://docs.gitlab.com/ee/user/group/index.html
Members are the users and groups who have access to your GitLab project. Each member gets a role, which determines what they can do in the project. The default roles available are:
Read more about permissions at: https://docs.gitlab.com/ee/user/permissions.html
Protect a Branch¶
In GitLab, permissions are fundamentally defined around the idea of having read or write permission to the repository and branches. To impose further restrictions on certain branches, they can be protected.
One very common use for this feature is to protect branches that deploy to Cascade environments from being merged into by members of the team that should not be deploying without review. This is commonly the case to live production environments.
Learn how to protect branches: https://docs.gitlab.com/ee/user/project/protected_branches.html