> 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-experience-in-a-usability-test.md).
# Manage participant experience in a usability test
***
On the **Overview** tab of your usability test, you can choose whether participants must download the Dscout browser extension or provide their name and email address to participate in your mission. Removing these requirements can get participants in and out of your study more quickly and with less work on their part, but less data will be collected. Review your options below to choose what makes the most sense for your research.
{% hint style="info" %}
**Note:** These settings are **only available when inviting your own participants to a desktop study**. If you’re auto-recruiting participants or conducting a mobile study, they will be required to provide their name and email address.
{% endhint %}
### Chrome extension
The Dscout browser extension lets you capture click data and generate heat maps for use during analysis. This is particularly useful if your usability test has task questions with Figma prototypes.
{% hint style="warning" %}
**Warning:** This setting cannot be changed post-launch.
{% endhint %}
By default, participants are required to install the extension to participate in desktop usability tests. However, you can disable this requirement if this data is not important to you.
{% hint style="info" %}
**Note:** This setting is only available on desktop usability tests. No browser extension is required for mobile studies.
{% endhint %}
| Setting | Description |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Extension required (default)** | Participants must have the Dscout browser extension installed to participate in your mission. If they don’t have the extension installed already, they will be prompted to do so before starting the mission. |
| **Extension free** |
Participants are not required to have the Dscout browser extension installed to participate in your mission.
Warning: Click data will not be collected and heat maps will not be generated for participants without the Dscout browser extension. We do not recommend this option if you wish to have this data during analysis.
|
### Participant sign up
By default, participants are required to provide their name and email address before they can participate in missions, including usability tests. However, you can disable this requirement if you don’t want your participants to have to complete this additional step.
{% hint style="warning" %}
**Warning:** This setting cannot be changed post-launch, and sign-up cannot be skipped when paying participants via Dscout.
{% endhint %}
| Setting | Description |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Require participant sign-up (default)** |
Participants must provide their name and email address to participate in your mission.
Note: Requiring participant sign-up does not automatically add a participant to Dscout’s Scout Panel. Requiring sign-up simply allows us to better assist if issues arise by collecting the participant’s name and email address.
|
| **Skip participant sign-up** |
Participants are not required to provide their name or email address to participate in your mission.
Warning: Be aware of the following when skipping participant sign-up:
Participant names will not be available (unless you ask for them at some point in your study).
Participant emails will not be collected.
Participants will not be agreeing to Dscout’s Terms and Conditions.
Data and entries will be deleted after 120 days.
Dscout cannot provide participant support if issues arise.
|
{% hint style="success" %}
**Tip:** If you choose to skip participant sign-up on a study with an informed consent document attached, participants are still required to agree to the document before they can begin. For more information, see [Add informed consent to a usability test](/usability-tests/create-a-usability-test/add-informed-consent-to-a-usability-test.md).
{% 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://help.dscout.com/usability-tests/create-a-usability-test/manage-participant-experience-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.