As more teams use GitLab, decisions about access, shared rules, costs, and platform changes affect people beyond the project where they began. The Platform governance and operating model pillar helps you make those decisions understandable and keep someone responsible for them as the platform grows.
Group structure, membership, and shared configuration work together. A group can make collaboration and administration easier while extending access or settings to every project beneath it. The starting questions are about the work: who should be able to do what, which responsibilities teams share, and where they need independence. GitLab's groups, roles, settings, and policies can then support those choices.
The differences between intended and actual behavior often show where attention is needed: a default that has become stale, an exception that has lost its owner, or a group move that would change who can reach the work. Clear responsibility helps teams address these problems without making every routine action wait for a central administrator.
The recommendations offer approaches to group design, access reviews, and maintaining rules and exceptions. If you're unsure where to begin, the pillar checklist can help you examine an existing project or a recent platform change.
Offering selection, deployment design, reliability, and scale also shape how GitLab is operated. Architecture Design covers those infrastructure choices; this pillar focuses on how people govern and use the platform.