Operations
Approvals
The human remains in control — reviewing, approving, and rejecting proposed infrastructure changes.
The approval boundary
Infraova operates autonomously across the monitoring, detection, prioritization, and proposal stages. At the approval stage, it stops. Every proposed change that would modify infrastructure — a DNS record, a configuration setting, anything that affects a client's domain — requires an explicit approval from an authorized operator before Infraova proceeds. The approval boundary is not optional and it cannot be bypassed.
Note
Infraova proposes → You approve → Infraova executes → Infraova verifies. The approval in the middle belongs to you.
Who can approve
Approval authority is determined by role. Organization owners and administrators can approve any proposal. Members can be granted approval authority for specific clients or domains. The access and permissions documentation covers the full role and permission model. When a proposal is generated, notifications are sent to all operators with approval authority for the affected domain.
Reviewing a proposal
To review a proposal, open it from the Issues view or from the approval notification link. The proposal screen shows the full context: the issue that triggered it, the diagnosis, the exact change being proposed, the provider it will execute against, and the expected outcome. Review all of this before approving — once approved, Infraova queues the change for immediate execution.
Approving a proposal
If you have reviewed the proposal and agree with the change, approve it. Infraova immediately queues the change for execution. You will receive a notification when execution completes and when verification finishes. The proposal status updates in real time — you can watch it move from Approved to Executing to Completed in the Issues view.
Rejecting a proposal
If you disagree with the proposed change, reject it. When rejecting, you can add a reason — this is recorded in the audit trail and helps context for future reference. A rejected proposal closes the issue as dismissed. If the underlying problem persists, Infraova will re-detect it on the next monitoring pass and may generate a new proposal.
Leaving a proposal pending
You do not have to act on a proposal immediately. Leaving it pending keeps the issue open and the proposal available for review at any time. Infraova will send periodic reminders for proposals that have been pending for an extended period, particularly for critical issues where delay may increase impact.
Approval history
Every approval and rejection is recorded in the audit trail with the operator who took the action, the timestamp, and any notes attached. The approval history is part of the operational record for each domain — it is the proof that every change to client infrastructure was explicitly authorized by a human before it was executed.