Set your org's pipeline rules
Pipeline rules hold every project in your organization to the same standard for its step into production. Each rule is checked whenever someone saves a project's pipeline: in Settings › CI Pipeline, and when a runner changes a pipeline for a task. What each rule asks and what Off, Warn and Block do: Pipeline rules.
Who can do this: an Org Owner or Org Admin. Others don't see the section.
Set a rule
- In the sidebar, select Settings, then Pipelines under Customize. Find the Pipeline rules card.
- Read Projects breaking it beside the rule. Point at the count, or tap it, for the projects that would be flagged; None means every saved pipeline already meets it.
- Pick the rule's Mode: Off, Warn or Block. Starting with Warn shows owners the warning on their next save without stopping them.
- For Production needs approval, also pick how many approvals it asks for, from 1 approval to 5 approvals.
- Select Save. To drop changes you have not saved, select Discard instead.
- Fix each project the rule flags, as below, then move the rule to Block if you want it enforced.

See which projects break a rule
Point at a rule's Projects breaking it count, or tap it, for the projects to fix. For each one, open the project's Settings › CI Pipeline, change the step into production and select Save (Fix a pipeline an org rule blocks).
Related
- What each rule and mode means: Pipeline rules.
- Every stage and step setting: Set up a project's pipeline.
- How approvals and releases run: Release to production.
- Who holds which role: Give someone access to a project.