How GitLab protects your IP
Aug 7, 2020Jordi Mon

Summary
This post details how GitLab's user access controls, including roles (Guest, Auditor, Developer, Reporter, Maintainer, Owner), protected branches, protected tags, push rules, merge request approvals (including security criteria and DevSecOps integration), and code owners, work together to protect intellectual property stored in repositories. It also covers audit events for tracing access and changes, and provides an example of managing permissions as code.
More from the SAML Single Sign-On (SSO) Integration trail
- A leaked personal access token shouldn't expose every project its owner can reach. Fine-grained PATs scope each token’s permissions to the job.
- Passkeys now available for passwordless sign-in and 2FA on GitLab
- How to set up GitLab SAML SSO with Google Workspace
- Strengthening GitLab.com security: Mandatory MFA
- Automating role-based access control (RBAC) at scale