Approvals, audit, and automation that respect the rules
Automation in Nexus never routes around governance. Sensitive actions pass through explicit approval, capture a reason, and land in the audit log, whether a person or an agent initiates them.
Governance first, automation second
- 01
An action is requested
A sensitive change, like a production promotion or a role change, is initiated.
- 02
Governance applies
The Approval Center routes it to the right approver, with a required reason.
- 03
It is decided and logged
The decision, the reason, and the actor are written to the audit trail.
- 04
Automation follows the rules
Deterministic resolution and health probes act only within the permissions set.
What is available, and what is planned
Approval Center
Route sensitive actions through explicit, recorded approval.
Reason-required actions
High-impact admin changes capture a written reason for the audit log.
Deterministic ticket resolution
Engineering-response tickets resolve through defined, repeatable rules.
Health probes
Automated checks watch service and provider health.
Customer-authored automation builder
A visual builder for company-defined workflows.
Scheduled & event triggers
Run automation on a schedule or in response to events.
Automate the routine, govern the sensitive
See how the Approval Center and audit trail keep automation accountable.