> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/challenges/automatic-enrollment-into-challenges.md).

# Automatic enrollment into challenges

Automatically enroll eligible customers in a challenge.

Enable automatic enrollment to add eligible customers to a challenge without requiring them to select **Join**.

### Enable automatic enrollment

1. Create a challenge, or open an existing draft.
2. In the challenge settings, enable **Automatically enroll eligible customers**.
3. Configure the challenge requirements, rewards, and eligibility restrictions.
4. Launch the challenge.

Eligible customers are enrolled automatically when they complete their first qualifying activity. Their qualifying activity counts toward challenge progress. They can view the challenge and their progress on the rewards website.

### Eligibility

Automatic enrollment follows the challenge's participation restrictions. These can include rewards-program status, member status, home location, and join-date rules.

Customers who do not meet those restrictions are not enrolled. Update the restrictions before launching the challenge to control who participates.

{% hint style="info" %}
Automatic enrollment removes the need to join. It does not change challenge requirements or reward rules.
{% endhint %}

For more challenge setup options, see [Creating a challenge](/features/challenges/creating-a-challenge.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/features/challenges/automatic-enrollment-into-challenges.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 `build a script that syncs our docs to a CMS` 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.