> For the complete documentation index, see [llms.txt](https://docs.guild.xyz/guild/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guild.xyz/guild/how-to-setup-requirements.md).

# How to setup requirements

Requirements are the conditions members must meet to access roles and their rewards.

#### Setting up requirements

**1. Add your first requirement**

* In the role editor, click **"Add requirements"**
* Choose from available requirement types
* Provide the data needed for the requirement
* Edit the requirement image and name, or leave empty to use default settings
* Toggle **"Should not satisfy"** to exclude members who meet this requirement<br>

**2. Configure requirement logic**

* **"Should meet ALL"** - Members must satisfy every requirement (AND logic)
* **"Should meet 1"** - Members need to satisfy at least one requirement (OR logic)
* **"Should meet X out of Y"** - Members need to satisfy a specific number of requirements

**3. Save and test**

* Click **"Save"**
* Use **"View page as a visitor"** to test the verification process

#### How verification works for members:

* Requirements are checked when members click **"Verify"**
* If they haven't connected a required account, they will see a **"Connect Discord"** button (or Twitter, wallet, etc.)
* Members can clearly see which requirements they have met and which they haven't

{% hint style="info" %}
Most requirements sync constantly - if someone stops meeting a requirement after getting the role, they automatically lose access.
{% endhint %}

#### Common mistake to avoid

**Adding requirements to existing roles:** If you add new requirements to a role that members already have, all current members will lose access to that role since they likely don't meet the new requirement. Create a new role instead or notify members before making changes.


---

# 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.guild.xyz/guild/how-to-setup-requirements.md?ask=<question>&goal=<endgoal>
```

`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.