Infraova
Resources›Guides›How to approve an infrastructure change

Guide

How to approve an infrastructure change

Walk through the approval workflow — what the proposal contains, how to authorize it, and what happens next.

AgencyEnterprise·4 min read

The situation

Approval is the human decision point in Infraova's operational loop. Infraova proposes; your team authorizes. This guide covers what happens at the moment of approval and what Infraova does immediately after.

Before you begin

A reviewed and understood remediation proposal
Confirmation that the proposed change is correct
Authority to approve DNS changes for the domain

The operational path

01Review proposal
02Authorize
03Execute
04Verify
05Record

The goal isn't just to find the error. The goal is to move from detection to a verified infrastructure state.

What could have caused this?

Cause

What changed

Possible impact

Pending proposal

Issue detected and fix prepared

Awaiting human authorization

Step by step

01Confirm the proposal is ready to approve

Before approving, confirm you have reviewed the proposal and understand what will happen.

What to check

✓You have read the issue description
✓You have reviewed the proposed record value
✓You have assessed the impact on the domain
✓You are confident the change is correct
02Authorize the change

In Infraova, approve the proposal. Your identity and the timestamp are recorded as part of the approval.

What to check

✓Click Approve in the proposal view
✓Confirm the action when prompted
✓The change is now authorized — Infraova will execute immediately

With Infraova

Infraova records the approving actor, the timestamp, the exact change, and the proposal that preceded it — a complete audit trail for every infrastructure change.

03Monitor execution

After approval, Infraova executes the change through the connected DNS provider.

What to check

✓The proposal status moves from Approved to Executing
✓Infraova applies the change via the provider API
✓The status moves to Verifying once execution is complete
04Review the verification result

Infraova automatically verifies the change by checking the live DNS state after execution.

What to check

✓Confirm the verification result shows the expected record value
✓If verification passes: the change is complete and recorded
✓If verification fails: review the failure and determine next steps

Expected result: The change is executed, verified, and recorded in the operational history.

You decide. Infraova executes.

Infraova can propose and execute an approved infrastructure change, but it does not independently decide to modify client infrastructure. Every proposed change requires explicit authorization before execution.

Infraova detects
↓Infraova diagnoses
↓Infraova proposes
↓YOU APPROVE
↓Infraova executes
↓Infraova verifies

Key takeaway

Approval is a single action with significant consequence. Review carefully, authorize deliberately, and let Infraova handle the execution and verification.

Turn this playbook into a continuous workflow

Without Infraova

Someone discovers the issue
↓Someone investigates manually
↓Someone decides what to do
↓Someone makes the change
↓Someone checks whether it worked

With Infraova

Monitor
↓Detect
↓Prioritize
↓Propose
↓Approve
↓Remediate
↓Verify
↓Record

The guide teaches you how to solve the problem once. Infraova keeps watching for it after you're done.

Want the product-level details?

Guides answer "How do I solve this?" Documentation answers "How does Infraova work?"

Stop discovering infrastructure problems manually.

Infraova continuously monitors your client and business infrastructure, identifies meaningful problems, proposes the next action, executes approved changes, and verifies the result.