> For the complete documentation index, see [llms.txt](https://gracy.gitbook.io/gracy-help-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gracy.gitbook.io/gracy-help-en/getting-started/admin-settings/reward.md).
# Reward
**How to set up Rewards?**
1️⃣ **Set Up Rewards (Optional)**
Go to the **Gracy Dashboard**, click **"Gracy Reward"**, and select **"Get Started"** to configure total rewards and per-recognition rewards. Please note that minimum charge is $20.
Reward Setting
2️⃣ **Enable Autocharge (Optional)**
In the **Payment Page**, set an auto-recharge threshold, amount, and monthly limit to ensure continuous rewards.
Autocharge
3️⃣ **Customize Rewards per Feature**
Adjust reward settings for **Grace, Whiteboard, and Shuffle** based on your company’s preferences.
Reward Setting by Features
💡 **Tip:** Encourage engagement by rewarding team members who actively contribute to workplace culture!
---
# 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://gracy.gitbook.io/gracy-help-en/getting-started/admin-settings/reward.md?ask=&goal=
```
`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.