// How-to
Review agent changes
When an agent wants to edit a governed document, it sends a change. You review the result before it becomes the version everyone uses next. Working documents allow direct agent edits; see How approval works.
Review a change
- Open the change from Inbox or its direct link.
The Summary tab opens first. It shows the author’s summary and the review timeline. If the author sent no summary, the page says so, and Ask for a summary opens a request with a note that asks for one. Select Send request to send it.
- Read the change, not only the summary.
Select the Changes tab to open the preview. The preview shows the document as it will look if you accept, with what was removed and what was added.
- Choose the outcome.
Use the action row after the timeline, or the pinned bar on Changes. Accept the change or select Request edits. The More actions menu beside Request edits offers Close change. Closing does not apply the change.
An agent proposing a change is not the same thing as changing the shared document. Your review is the boundary between those two events.
Request a useful revision
- Open the change and compare it with the current document.
- Anchor feedback to the relevant text when inline comments are available.
- State the required change and its reason.
- Use Request edits to send the work back. A discussion comment alone is not the same decision.
- Review the revised change before accepting it.
Understand each decision
- Accept: applies the reviewed change as a new document version.
- Close change: closes the change without applying it. The change and its discussion stay in its history.
- Request edits: returns the change for revision with your feedback.
The decision applies to the change you reviewed. Read the body and source evidence as well as the summary. An agent review can supply advice; it does not replace your approval.
When the document changed during review
A change can become stale when another change reaches the document first. Check its relationship to the latest version. If the app offers Apply change to current version, review the merged result. If the changes conflict, request a revision against the current document. Do not assume an old preview includes another reviewer’s later changes.
Roll back to an earlier version
A rollback makes a governed document the same as one of its earlier versions. It does not delete anything. It saves a new version with the earlier content, and every later version stays in History.
- Find the version.
Open the document’s History and select Roll back to V3… on the version you want, or select it in the banner while you view that version. A version that already matches the current version shows a Same as current label instead.
- Check what changes.
The dialog names the new version, for example “Creates V9 with the same content as V3.” To compare versions first, select Show changes on the version in History. You can add a reason of up to 500 characters. History shows the reason with the rollback.
- Choose how to roll back.
Roll back now saves the new version at once. Propose rollback sends a rollback for review, and the change page opens.
If the result is not confirmed, for example after a lost connection, the dialog offers Check now. It looks up the request again and never sends a second rollback. Working documents, images and archived documents do not offer rollback. Unarchive an archived document from its ⋯ menu first.
Review a rollback
A rollback change is titled “Roll back to V3”. Its summary says “Makes the document the same as V3” and shows the reason, if one was given. Its content is fixed, so it offers no Request edits, Update or Apply change to current version. The card offers Accept change and Close change. To decline the rollback, select Close change. In Inbox the row reads “Roll back to V3”. In History an open rollback has a dashed record with a Proposed badge and reads “Rollback to V3”. It is not a version yet. The person who proposed it can select Dismiss to close it, and Undo in the message brings it back. An accepted rollback reads “Rolled back to V3”. When the proposer and the approver are different people, History names both.
If the document changes after the rollback was proposed, the change page says so:
- Roll back again compares the new current version with V3 and replaces the change’s content.
- If the current version already has the same content as V3, nothing is left to roll back. Select Close change.
- If another rollback to V3 is already open for the current version, select Open the other rollback to review it.
Agent rollbacks
Agents can propose a rollback. A human decides. An agent uses the artifactbridge_propose_document_patch tool with one of these parameters:
rollback_to_version: the stored version number, for example3.rollback_to_version_id: the exact stored version id.
Use only one of them. Do not send document content, such as proposed_md, with a rollback. The tool description says: “Use rollback_to_version to propose going back to an earlier version. A human decides.”
Review returned Word files
A redline is a Word document with tracked changes. Use Add redline to select the returned .docx and identify which document or version it applies to.
- Inspect every extracted edit.
- Accept an edit, reject it with a comment, or acknowledge an edit outside the main text when that is the offered action.
- Decide every edit, then accept the overall change to publish the result.
- Use Download .docx for the reply file and copy the decision summary when you need to send a response.
Downloading prepares the file. You still send it to the other party yourself. Check the reply file before sending, especially for formatting or changes outside the main text.
Document comments and change comments
A document comment concerns the document. A change comment concerns the proposed change. Reply in the existing thread to keep the discussion together. When an agent’s revision addresses a document thread, linking the change lets its acceptance resolve the linked discussion. Provider-origin comments follow the source’s workflow.