> 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-guild-works.md).

# How Guild works

Guild organizes your community using three building blocks: Requirements, Roles, and Rewards.

Think of it like a simple rule system:

**Requirements** → What people need to do

**Roles** → Groups you organize people into

**Rewards** → What group members get

<figure><img src="https://2741276286-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYUpDHzd4HDKO8hEPSNOZ%2Fuploads%2FsOMI4b0zCWFZQ1BIus3K%2FGuild%20UI.png?alt=media&amp;token=6d3cc478-b293-47cc-baa4-fd413aa45e25" alt=""><figcaption></figcaption></figure>

### Requirements

Requirements are the conditions people must meet. These can be:

* **Onchain activity** - Own $TOKEN/NFT, make 5 transactions on Ethereum, interact with XYZ smart contract
* **Social proof** - Follow on X, hold Discord role “Member”, verify email
* **Guild activity** - Have 50+ points, have XYZ guild role
* **Time-based** - Have a Discord role before Jan 1st, have a transaction in the last 7 days on Base

You can combine requirements with AND/OR logic. Example: "Hold $TOKEN AND Follow on X" or Hold $TOKEN OR Stake $TOKEN.

Set “Should not satisfy” requirements to exclude people.

### Roles

Roles are groups you create based on requirements.

Examples:

* Role: **Early Supporter** *role* - Requirement&#x73;*:* Waitlist subscriber AND Genesis NFT holder&#x20;
* Role: **Active User** - Requirements: Have an interaction with the XYZ contract in the last 30 days AND hold a Discord role
* Role: **OG Member** - Requirements: Have the “Early Supporter” AND the “Active Contributor” role AND Stake $TOKEN

Members automatically gain or lose roles when they meet or stop meeting requirements. No manual management needed.

### Rewards

Rewards are what role members get once they meet requirements. These include:

* **Platform access** - Discord/Telegram groups, content, forms
* **Digital rewards** - Points, NFTs and tokens
* **Real perks** - Merchandise, event tickets, early access

### Example flow

1. Create role: "Token holders"
2. Set requirement: "Hold 500+ $TOKEN"
3. Add rewards: Token holder Discord role + 5 points
4. Members with 500+ tokens automatically get the Discord role and 5 points
5. If they sell tokens and drop below 500, they lose role & rewards automatically

Set rules once. Guild handles everything else.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guild.xyz/guild/how-guild-works.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
