Before you start
- A formal change request attached to the correct client workflow.
- A clear understanding of whether the work is already authorized.
- A way to test or observe the requested outcome.
Confirm the recorded scope
Read the requested change before touching production. Confirm the client, workflow, requested outcome, owner, and due date. Correct the record before implementation if the request is incomplete.
Choose the correct authorization path
Choose Start work when the request is already authorized or does not require separate client approval.
Choose Create client approval link when the client still needs to decide. AgentHub freezes the exact request for 14 days and shows a secure link once. Copy it and share it through the client's existing channel.
After the approval page opens successfully, the change record shows Approval link first opened with the time. Refresh the change record to check again. This confirms a page open, not who opened it.
The client can approve or request changes without an account. Approval moves the request to Approved but does not start work. Requested changes return it to Triaged so you can correct the scope and issue a new link.
If approval already happened elsewhere, open Approval happened somewhere else and record the external decision. That fallback also stops at Approved.
Record what was implemented
Add the implementation details that a later reviewer would need to understand the work. Under Implementation evidence, choose Add evidence for the relevant repository, pull request, commit, test, deployment, or other durable reference.
References remain Workspace only by default. Select Include this reference in new client briefs only when the URL and label are safe for the client. Then choose Ready to verify.
If the workflow is connected through a supported n8n or Make sync, AgentHub attempts to capture the latest safe structural version. Credentials, node parameters, field values, and execution payloads are excluded.
Review the before-and-after evidence
When both snapshots exist, review the structural comparison and fingerprints. A partial or unavailable comparison is an evidence limit, not a successful verification result.
History starts when AgentHub captures the baseline. It does not reconstruct workflow versions that were never stored.
Test the requested outcome
Review and edit the targeted verification plan, then perform the checks in the source platform or production environment. Record the result that you actually observed.
- Pass verification and reconcile scope: the requested outcome worked, the evidence is sufficient, and you are ready to compare the implementation with the recorded scope.
- Return to work: the result failed and implementation must continue.
- Wait for evidence: the result may be correct, but the evidence is not yet sufficient.
Reconcile the implementation to the recorded scope
Choose Yes, it matches when the implemented result stayed inside the recorded scope.
Choose No, it differs when implementation moved beyond or away from that scope. Then select Revised approval was captured and enter the approval reference, or select Close with an unresolved scope difference and describe what remains unresolved.
The unresolved path is an explicit exception, not a hidden success. It stays visible in the change record and in client briefs that include the change.
Verify it worked
- A passed request shows Verified passed, the verification note, who recorded it, and when.
- The same record shows the filed scope outcome and any revised approval reference or unresolved exception note.
- Technical references show whether they are private to the workspace or approved for new client briefs.
- The closed record remains frozen in the audit trail.
- The record never uses a missing snapshot or missing test result as proof of success.
Common issues
I expected AgentHub to send the approval link
Copy the secure link when it is created and share it in the client channel you already use. AgentHub does not choose a recipient or send it automatically.
The approval link shows as opened
This means the approval page successfully exchanged its secure token. It does not prove the intended client opened it, because bearer links can be forwarded and some automated scanners can run JavaScript.
The client requested different scope
Their response returns the record to editable review. Choose Edit request, save the corrected scope, and create a new approval link.
I need to change a request while a link is active
Choose Revoke and edit request. The old link stops working and the record returns to Triaged.
The after version is missing
Confirm the workflow is assigned to a supported connection and sync it again. You can still verify manually and record the evidence available.
I cannot add or remove implementation evidence
Evidence can be changed only while the request is in progress or verification. Start the work first. Once the request closes, its evidence is frozen.
I expected GitHub to sync automatically
Current GitHub support stores links you file. AgentHub does not connect to the account, read source code, or import pull requests and commits automatically.
The verification plan is not right
Edit it before testing. Suggested checks are a draft and do not mark anything complete.
I cannot close the change
A completed change requires a passed verification result, result note, and scope reconciliation outcome. Record the production evidence, then choose whether the result matches the recorded scope. A scope difference also requires either a revised approval reference or an unresolved exception note.