Teams need room to adapt their work and clarity about which requirements still apply. A shared setup can support both, but its effect depends on how GitLab delivers it. Copied files, included components, inherited settings, and security policies have different behavior. Confusing them can leave a required check removable or make a supposedly optional change block delivery.
Explain what happens when a team changes its setup
A project template provides a starting copy of files and configuration.1 The new project can evolve independently to suit the team's needs. Updates to the template won't reach those projects automatically, so keeping existing projects aligned needs a separate update process.
A CI/CD component lets projects reuse maintained pipeline logic at a selected revision. Pinning a reviewed release or commit SHA makes changes predictable and gives a team an opportunity to test an update. It also means someone needs to keep track of supported versions and help consumers move away from retired ones. An ordinary component include can be changed or removed by someone who controls the project's pipeline configuration.
Group settings can supply defaults or restrictions, depending on the setting. Explain whether a choice affects only future projects, continues to apply to existing projects, or can be changed locally. With protected branches, for example, a project can't edit an inherited group rule but can add a matching rule; push and merge permissions are then combined using the most permissive result. The presence of a shared rule alone doesn't establish the final restriction.
These explanations help a team make a safe local decision. They also help the platform owner choose a mechanism that actually supports the requirement.
Connect a requirement to the behavior that enforces it
A compliance framework identifies projects that have particular requirements.2 It can also help select the projects a security policy covers. Applying the label alone doesn't establish that every requirement is enforced. Identify the setting, policy, or review process that supplies the required behavior.
For example, a company may require a security check before a release. A template can teach teams how to run it. If retaining the check is mandatory, a policy can require the relevant jobs across the intended projects.3 The policy still needs the right scope, branch coverage, and pipeline behavior. Check that the required jobs run on representative changes and that the expected response occurs when a check fails or its result is missing.
Make the reason for each rule and the freedom to adapt it understandable to delivery teams. Include who maintains it and how a team can request an exception. A requirement with no usable support path encourages workarounds when a project encounters a legitimate incompatibility.
Introduce shared rules with feedback and recovery
A required rule can affect many projects at once. Try it on representative work before expanding its coverage: different default branches, pipeline arrangements, and access patterns can expose assumptions that a simple example misses. Review the results with contributors and update instructions where the rule changes their work.
Protect the projects that hold security policies and require review of policy changes. Limit who can change the policy links as well as the policy files. After a change, confirm that the policy is active on the intended projects and that their pipelines or merge requests behave as expected. Keep a clear owner and recovery action for a rollout that blocks legitimate delivery.
Check existing projects separately. A default compliance framework applies to new and imported projects; it doesn't update existing ones. A successful rollout to newly created projects therefore leaves a separate question about older projects.
If projects still use compliance pipelines, migrate them before enabling pipeline execution policies on the same projects. Compliance pipelines are deprecated, and combining the two can produce duplicate jobs, missing checks, or pipeline failures. That interaction makes the migration sequence part of preserving the required behavior.
Further Reading
Notes
-
Custom group project templates are available in Premium and Ultimate. They make a common setup available through GitLab's project-creation workflow. ↩
-
Compliance frameworks are available in Premium and Ultimate. Compliance requirements and controls are only available in Ultimate. ↩
-
Pipeline execution policies are available in Ultimate. They can require jobs independently of an application's own pipeline configuration. ↩
- Platform rules teams can understand and maintain connects the choice of mechanism to ownership, rollout, and exceptions.
- Design and version CI/CD components helps you maintain shared configuration that teams can adopt deliberately.
- Configure compliance frameworks covers assignment, defaults, requirements, and controls.
- Apply policies to the intended projects explains how links, inheritance, and scope determine coverage.
- Configure pipeline execution policies covers required jobs and the interaction with existing pipeline configuration.