> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/planning/members/rewards.md).

# Rewards

This page shows you a list of [rewards](/event/general/rewards.md) assigned to this person. From here you can [give](/event/general/rewards.md#give) those rewards. There is also a *Give all* button that allows you to mark all rewards as given at once.

You can [assign](/event/general/rewards.md#assign) new rewards to this person via the button on top of the page.

When giving [ticket rewards](/event/general/rewards/ticket-rewards.md), the user will receive an email with a link where they can configure their choice and download tickets.

{% hint style="info" %}
If you mark multiple rewards as *given*, the member will only receive 1 email per 10 minutes. That means if you quickly give out 2 ticket rewards, only one email will be sent. We do not want to spam the inbox and the link in those emails is always the same.
{% endhint %}

{% hint style="warning" %}
If you give a ticket reward and the member has selected tickets, destroying that reward in the settings will cancel all those tickets.
{% endhint %}


---

# 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.eventication.com/event/planning/members/rewards.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.