> 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-rewards.md).
# How to setup rewards
Rewards are the benefits members receive when they qualify for roles. They are what makes your Guild valuable and give members clear incentives to engage with your community.
### Setting up rewards
**1. Add your first reward**
* In the role editor, click **"Add reward"**
* Choose from available reward types (Discord, Telegram, NFT, Points)
* Provide the configuration details needed for the reward type
* Add more rewards if you want
**2. Save and test**
* Click **"Save"**
* Use **"View page as a visitor"** to see how rewards appear to members
* Qualified members will automatically see available rewards
### How rewards work for members
* Rewards are visible for all members but locked until requirements are met
* Rewards become available to claim once the requirements are met
* Members can claim rewards immediately by clicking the **"Claim"** button
* Rewards are granted instantly, but assigning Discord roles can take time due to Discord rate limits (members see a time estimation for when the role will be assigned)
* Members can see which rewards they have claimed
{% hint style="info" %}
Most requirements sync automatically, so if someone stops meeting requirements and loses role access, they also lose reward access immediately.
{% endhint %}
### Common mistake to avoid
**Changing reward configurations:** If you remove/re-add a reward for an existing role, role members have to reclaim the rewards.
---
# 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-to-setup-rewards.md?ask=&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.