In GitLab, to ensure strict code review, you can require a specific number of approvals on a merge request by different users before being able to merge it. You can undo an approval by removing it after the fact.
Documentation
An admin can email groups of users based on project or group membership, or email everyone using the GitLab instance. This is great for scheduled maintenance or upgrades.
Documentation
Ensure that disk space usage is under control.
Documentation
Group owners can prevent new members from being added to projects within a group.
Documentation
Control the technology and key length of SSH keys used to access GitLab
Documentation
GitLab Enterprise Edition gives your Admin’s the ability to automatically sync groups and manage SSH-keys, permissions, and authentication, so you can focus on building your product, not configuring your tools.
Documentation
To maintain the integrity of your code, GitLab Enterprise Edition gives admins the ability to view any modifications made within the GitLab server in an advanced audit log system, so you can control, analyze and track every change.
Documentation
Auditor users are users who are given read-only access to all projects, groups, and other resources on the GitLab instance.
Documentation
Manage access and permissions with five different user roles and settings for external users. Set permissions according to people’s role, rather than either read or write access to a repository. Don’t share the source code with people that only need access to the issue tracker.
Documentation
Sign commits and prove that a commit was performed by a certain user.
Documentation
You can mark a secret variable as “protected” to make it available only to jobs running on protected branches, therefore only authorized users can get access to it.
Documentation
A single repository in Git is typically a number of times smaller than the same repository in SVN.
Documentation