Configure deployment protection
Deployment protection evaluates a change at a supported delivery step. It requires both Proofline settings and a connected deployment mechanism.

Check the delivery path#
Open the environment's Setup → General page. Confirm that its delivery mechanism matches the system that deploys the repository.
For GitHub Actions, follow the environment's GitHub protection rule setup. For Cloud Build, connect a trigger that requires approval.
A GitHub Actions workflow-only target uses workflow evidence without a GitHub Environment or custom protection rule. It does not provide a deployment-environment gate.
Connect a Cloud Build gate#
On the environment's Setup → Delivery page, add a gate under Cloud Build deployment protection. Choose the Repository target, Cloud Build project and region, and Deployment trigger ID. Enter the required substitution names and values, then select Add gate.
The optional Image digest substitution names the substitution each held build sets to its deployed image's sha256 digest. Use a name beginning with _, distinct from _SHA and the required substitutions.
Other delivery mechanisms may not send a deployment event. Pull request reviews can still run, but they do not establish a deployment gate.
Choose the review policy#
- Open Settings → Review policy → Automation.
- Review the deployment protection settings.
- Choose the blocking severity when the control is available.
- Check the environment's deployment review settings.
- Complete the protection setup shown for its delivery mechanism.
The severity choices distinguish serious and critical findings from every supported finding, warnings and notes included. Choose the policy your team intends to enforce.
Inspect a deployment review#
Filter Reviews to deployment reviews, then open the result for the environment. Check the assessment and any recorded decision before proceeding.
An unavailable evidence source can leave the assessment incomplete. Resolve the reported condition rather than interpreting an incomplete result as approval.
Open the environment's Decisions page to inspect recorded decisions. Each row names the repository, the commit, the workflow run or build, and the review, with the decision, its policy, and when it was made. Open Details for the reason and the assessment evidence. An allowed decision is permission under the policy, not verification of the revision. Deployment processing failures did not record an authorization decision. Follow Open associated review when available to investigate the failure. Older records may fall outside the loaded history.