> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/usability-tests/create-a-usability-test/manage-participant-limit-and-incentive-in-a-usability-test.md).
# Manage participant limit and incentive in a usability test
Your research needs (and your research budget!) will determine how many participants your mission can have—and of course how much you’ll pay them. These are both managed on the **Overview** tab of your mission prior to launch.
### Participant limit
Your mission’s participant limit determines how many people can complete your mission. You can have as few as one participant or as many as 200 in a single usability test. When your limit is reached, your mission is automatically closed to new applicants.
{% hint style="info" %}
**Note:** When inviting your own participants, closure of your study is based on the number of processed submissions. You may receive more than your desired number of submissions if additional participants submit responses before all other submissions have finished processing.
{% endhint %}
**To set your mission’s participant limit:**
{% stepper %}
{% step %}
Navigate to the **Overview** tab of your mission.
{% endstep %}
{% step %}
Click anywhere in the **Mission details** section.
{% endstep %}
{% step %}
Enter a **Participant limit** (1–200).
{% hint style="info" %}
**Note:** When inviting your own participants to a mission, you'll first need to toggle ON the **Participant limit** setting. Then, you can enter your desired limit. If you're paying your participants through Dscout, a limit is required.
{% endhint %}
{% endstep %}
{% step %}
Click **Done**.
{% endstep %}
{% endstepper %}
Now, your participant limit is set. Once your mission receives your designated number of responses, recruitment will stop and your mission will close.
{% hint style="success" %}
**Tip:** If you need to gather more insights later, you can edit your participant limit and re-launch. For more information, see [Edit a launched mission](/study-basics/edit-close-or-relaunch-missions/edit-a-launched-screener-or-study.md).
{% endhint %}
### Mission incentive
Your mission incentive determines how much each participant will receive as a thanks for their input. The incentive should be reflective of the time and effort required on their part, and it should also be enticing enough to encourage applicants if you’re auto-recruiting.
{% hint style="success" %}
**Tip:** For advice on what to offer your participants, see [How much should a usability test pay?](/usability-tests/what-are-usability-tests-in-dscout/how-much-should-a-usability-test-pay.md)
{% endhint %}
**To set your mission’s incentive:**
{% stepper %}
{% step %}
Navigate to the **Overview** tab of your mission.
{% endstep %}
{% step %}
Click anywhere in the **Mission details** section.
{% endstep %}
{% step %}
**(Studies with bring-your-own participants only)** Select whether you want your participants to be **Paid via Dscout**. You have the following options:
* **Yes:** Dscout issues payments to participants via PayPal seven days after their submissions are received. In those seven days, you can review submissions for quality before each payment is sent. A participant limit is required when Dscout manages payments.
* **No:** You are responsible for issuing payments to your participants and can do so using whatever payment method you choose.
{% endstep %}
{% step %}
Enter an **Incentive per participant**. Your mission’s **Incentive total** is automatically calculated based on your entry here and your participant limit.
{% hint style="info" %}
**Note:** Minimum and maximum incentives vary depending on your recruitment method. Refer to the guidance displayed beneath the **Incentive per participant** field in Dscout for more information.
{% endhint %}
{% endstep %}
{% step %}
Click **Done**.
{% endstep %}
{% endstepper %}
Now, your mission’s incentive is set. This amount will be displayed to participants when they apply to or begin your mission.
---
# 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://help.dscout.com/usability-tests/create-a-usability-test/manage-participant-limit-and-incentive-in-a-usability-test.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.