> For the complete documentation index, see [llms.txt](https://docs.b2ihealthcare.com/snow-owl-authoring-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2ihealthcare.com/snow-owl-authoring-platform/collaborative-authoring/task-editor/review-changes-page.md).
# Review Changes Page
Reviewers can review the task's changes submitted by the authors on the **Review Changes Page** where the individual changes are listed.
Each listed individual change can be either approved or rejected by the reviewer. Clicking on a row in the *Review* column invokes a dialog where the status of the particular change can be set to **`Rejected`** or **`Approved`**.
Review changes individually
Changes can also be approved or rejected in a bulk manner using the checkboxes in front of the changed items and then pressing **`Accept Selection`** or **`Reject Selection`** buttons.
{% hint style="info" %}
The checkboxes appear regardless of the status of the task, but only for the user who is assigned as reviewer.
{% endhint %}
Bulk review changes
The content of the table can be  filtered based on the approval status and the change type of the individual items by selecting the filter icon from the editor's toolbar. The different filter types can be mixed, i.e. it is possible to select a filter for the approval status together with a change type.
Filter options for review
{% hint style="info" %}
Changes without approval or rejection specified are considered to be approved by default.
{% endhint %}
{% hint style="warning" %}
The Review Page is limited to reveal a maximum of 50 000 changes. After performing numerous changes on a Task the page might not contain all the changes.
{% endhint %}
Once the individual components are reviewed, the reviewer can save and submit the results by clicking on the  button located on the top-right side of the task editor. The button brings up the **Task Review Dialog** where the reviewer can decide on how to proceed within the task workflow:
* **`Approve`** - the changes submitted are complete (even with optionally rejected individual changes), no further authoring needed
* **`Request Changes`** - the changes submitted are incomplete and require further authoring
Submit Changes Dialog
Once each reviewer assigned to the task has submitted their review, the workflow can proceed based on the results of the reviewers. If every reviewer has accepted the changes, the reviews can be acknowledged and the task content can be prepared for promotion by clicking on the  button visible on the **Task Editor**'s **Overview Page**. In case even one of the reviews has requested changes, the only option available is  button to complete the requested changes.
After a task is verified, the content can be promoted by the reviewer by pressing the button located on the **Task Editor.**
{% hint style="info" %}
If there were individual items marked as rejected during the reviewing stage, the user is prompted with the possibility of creating a new task from the rejected items. This way rejected items can be further authored under a newly generated task that will have the same properties as the original one.
{% endhint %}
Dialog of creating new task
The original task's status will be set to **`Closed`**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.b2ihealthcare.com/snow-owl-authoring-platform/collaborative-authoring/task-editor/review-changes-page.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.