# Consensus

**Consensus** determines how many labelers must agree before a label is automatically accepted in a project. If a label does not meet the consensus threshold, it is marked as **conflict**.\
\
Currently, two types of consensus are available:

1. **No consensus** – Every label is marked as a conflict and must be resolved by a reviewer.
2. **Peer review consensus** – Labels are automatically accepted once the required number of labelers agree. For example, if the consensus is set to 1, every label will be automatically accepted.

## No consensus

To enable **No consensus**, follow these steps:

1. During project creation, go to **Step 4.**
2. In the **Conflict resolution** section, select **No consensus**.

![](/files/6R50B0rliTVVaSauqc38)

### **Use case**

The **No consensus** setting can be used if you want your reviewers to review every label applied by the labelers. All applied labels will be considered as conflicts, and reviewers must manually accept or reject them in reviewer mode.

## Peer review consensus

**Peer review consensus** is explained in the [QA/Review](https://docs.datasaur.ai/workspace-management/workspace#qa-review) section.


---

# 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.datasaur.ai/data-studio-projects/creating-a-project/consensus.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.