Deployment Approvals

You can require every deployment in a project to be approved before it runs. With approvals on, anyone can request a deployment, but it waits for sign-off from someone with permission. This gives the team a checkpoint before changes reach production.

Deployment approvals are configured per project, under Settings → Deploy approvals.

On the Deploy approvals tab, switch on Require approval to deploy. Deployments in the project are then held until approved.

Only project admins can change this setting; others can see it but not change it.

Anyone with the Approve deployments permission can approve a deployment:

• Project admins, who have it by default.
• Anyone with a custom role that grants Approve deployments.

This separates who can request a deployment from who can approve one. For example, editors can deploy to staging while a release manager signs off on production.

1. A team member starts a deployment as usual.
2. With approvals on, the deployment is held instead of running.
3. It appears under Pending deployments on the Deploy approvals tab, showing the app, who requested it, and where it would deploy (provider, region, and machine size).
4. An approver selects Approve to run it, or Reject to stop it.

• Custom roles — grant the Approve deployments permission.
• Audit logs — review approvals and other activity.