Deployment Management → Governance lets administrators control how changes reach each environment — development, test, staging and production — and see who did what.
Environment policies
Under Environments, edit a policy to turn on any of these:
- Require approval — deploys, redeploys, rollbacks and scaling wait for an administrator to approve them. You can allow requesters to approve their own changes.
- Require a change request reference.
- Require a rollback plan.
- Only allow changes in maintenance windows — set one or more weekly windows in UTC.
Approvals
The Approvals tab lists everything waiting for approval or for a maintenance window. Approve or Reject each request, with a reason when rejecting. Pending requests can also be cancelled. Recently decided requests stay listed below.
A change made outside a maintenance window can be scheduled for the next window. Administrators can also choose Override — run now.
Audit trail
The Audit trail records every change to deployments, Compose files, variable groups, policies, Git repositories, users and settings, with who made it and when. Search it or filter by area.
Example: approval followed by a maintenance window
For Production, require approval, a change request reference and a rollback plan, and allow changes only on Sundays from 02:00 to 03:00 UTC. That window is 07:30 to 08:30 in India. Keep Requesters may approve their own changes off when you want another administrator to review.
- Submit a production deployment with reference CHG-1042 and a concrete rollback plan, such as return to verified revision 3.
- An administrator opens Governance → Approvals and reviews the requested change.
- Approval outside the permitted window can leave the operation scheduled. Inspect its status rather than assuming approval means it has run.
- After execution, check History for the new revision and health. Administrators can review Audit trail for the recorded actions.