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 and requested outcome. The owner and due date appear below the record title, and the next step is right under them. Correct the scope with Edit scope before implementation if the request is incomplete. Change the owner or due date under More options.
Choose the correct authorization path
Open Already authorized? and choose Start the change when the request is already authorized or does not require separate client approval. This records the request as in progress. It needs the workflow: on a request saved without one, choose Set the workflow first. You implement the change in your existing tools; AgentHub does not run it.
Choose Get client approval when the client still needs to decide. AgentHub shows the saved scope in full; choose Create client approval link to freeze it for 14 days and show a secure link once. Copy it and share it through the client's existing channel. Unsaved scope edits must be saved or discarded first.
The approval page asks Does this match what you need? and says who sent it. The client chooses Approve scope, or Request changes and says what should change. While you wait, the record shows when the link expires and when it was first opened; that confirms a page open, not who opened it. While the record is open on your screen it checks for the decision every minute, and Check for the requester's decision looks right away.
Approval moves the request to Approved but does not start work. Requested changes return it to Triaged with their note, so you can correct the scope and ask again.
If approval already happened elsewhere, open Approved somewhere else? and choose Record approval. That fallback also stops at Approved.
Record what was implemented
Answer What did you change? the way you would tell the client; it is required before Ready to verify. Once the change is verified, new client updates show it under What we changed, and the summary uses it; a line with a link, a password or a key is left out. Under Evidence, choose Add evidence for the pull request, commit, test run, deployment, or other durable reference.
Evidence remains Workspace only by default. Select Include this reference in new client briefs only when the URL and label are safe for the client.
If the workflow is connected through a supported n8n or Make sync, AgentHub attempts to record the latest safe structural version. Credentials, node parameters, field values, and execution payloads are excluded from that version. n8n setup reading, when it is on, is separate: it keeps summaries of how the workflow is set up, for answers.
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 records the baseline. It does not reconstruct workflow versions that were never stored.
Check the requested outcome
The record asks What did you find? Open Write down what you will check to put the checks on the record before you run them, then do them in the source platform or production. If the assistant wrote checks before you revised the scope, they are marked Written for an earlier scope: open Check and keep these, edit them, and choose Keep these checks. To have the assistant redo them, choose Prepare a new draft while the request is still being scoped. Under What did you see?, write what you did and what you saw. It is optional for a pass, but it goes into the client update, and an empty box is recorded as No checks written down rather than hidden. Then choose one answer under Did it work?; nothing is chosen for you.
- Passed: the checks passed. Say whether it stayed inside what was asked, then Mark verified.
- Failed: write what failed, then Record the failure and go back to the change. The change continues.
- Not enough evidence: Go back and wait for evidence. The result may be right, but the evidence is not there yet.
Say whether it does what was asked
The form asks Does it do what they asked, and nothing more? Choose Yes when the result stayed inside what was asked. The button becomes Mark verified.
Choose It differs from what was asked when the change went beyond or away from it. Then say The client approved the difference elsewhere and where, or Close with the difference noted and describe what remains different. The button becomes Mark verified, difference noted.
A noted difference is an explicit exception, not a hidden success. It stays visible on the change record and in every client brief that includes the change.
Verify it worked
- A verified request shows Verified, how it was checked or No checks written down, who recorded it, and when.
- The same record says whether the result matched what was asked, with any approval reference or noted difference.
- 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 responded, but the record has not changed
The record checks every minute while it is open on your screen. Choose the check button under the link to look now, or reload the page.
The client requested different scope
Their response returns the record to editable review with their note. Choose Edit scope, Save scope, then Get client approval again.
I need to change a request while a link is active
Open Manage approval link and choose Revoke and edit the scope. The old link stops working and the record returns to Triaged.
It says the scope changed after I reviewed it
Someone saved a different scope, or changed the approval link, after your page loaded. Nothing was frozen or created. Check the saved scope now shown, then choose Create client approval link again if it is right.
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.
The button says Record the result and stays disabled
Choose Passed, Failed or Not enough evidence. For Passed, also say whether the change does what was asked, and if it differs, how the difference was handled. The button is named for the result once the answer is complete.