# 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**.

![](https://448889121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbjY0HseEqu7LtYAt4d%2Fuploads%2Fgit-blob-37bcc2d9b34fe48dd87c1b972c706c4ab0b18c6a%2FPCW%20-%20Step%204%20-%20no%20consensus.png?alt=media)

### **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.