# Review

Tasks in a *Review* stage will be shown to a user with at least review permissions (e.g. Reviewers, Leads, and Managers) when they click on *Start Reviewing* for reviewing.

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2F1jnLGeYvuUJIFojxxaL4%2Fimage.png?alt=media&#x26;token=38b6f7c3-aba4-49a1-bbed-4efc2027a4d2" alt="" width="293"><figcaption></figcaption></figure>

{% hint style="info" %}
Once a reviewer is assigned to review a task in a Review stage, they will remain the assignee for that task for this stage even if, later, the task moves to other stages and then comes back to the original Review stage.

Therefore, if someone reviews a task, and then it gets sent back to the same review stage as a result of other workflow actions later, it will be reviewed by the same reviewer.
{% endhint %}

#### Output

The *Review* stage has two outputs, one for each of the review options. If a reviewer, while reviewing, clicks on *Accept*, it is sent from the *Accepted* output. Alternatively, if the reviewer clicks on *Reject*, it is sent from the *Rejected* output.

This allows you to create workflows where, for example, you send rejected tasks to a second review, or back to labeling [as shown in this previous section](#adding-stages).

#### Output Percentages

The percentages displayed on the stage indicate the percentage of times tasks have been sent out of the Review stage from the Accepted or Rejected outputs.

For example, if tasks left the Review stage 100 times, and 76 of these times it was through the Accepted output, then the acceptance percentage displayed will be 76%.

{% hint style="info" %}
Please note that this includes tasks which go through the Review stage multiple times.

For example, in a new Review stage, if a task is initially rejected, this it will count as a rejection, and the rejection rate will go to 100%. Later, if that same task is sent back to this Review stage and accepted, this will count as an acceptance, but for the purposes of the percentage displayed on screen, the earlier rejection is **not** removed. The percentages displayed at this point would then be 50%/50% as there has been one rejection and one acceptance.
{% endhint %}

#### Options

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FDR2F5wVioUZA310odSR4%2Fimage.png?alt=media&#x26;token=29162a78-10f2-4021-b001-b7926909ee6b" alt="" width="375"><figcaption></figcaption></figure>

**Read Only.** By activating this toggle, reviewers will not be able to make changes to the annotations. They will only be able to click on *Accept* or *Reject*.

**Bulk Accept/Reject**. From the left dropdown, you may select all tasks in the stage or only a particular batch. Then, by clicking on Accept or Reject, you can bulk accept/reject them. This is akin to clicking on "Accept" or "Reject" on all tasks.

**Assignees.** By default, tasks in a *Review* stage are shown to any user with review permissions who clicks on *Start Reviewing*. To restrict tasks to specific reviewers, click on "Select Reviewer" and choose one or more users from the dropdown. This ensures that only the selected user(s) can review tasks in this stage.


---

# Agent Instructions: 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:

```
GET https://docs.imerit.net/core-concepts/workflow/review.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.