> 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/recruit-participants/dscout-scout-panel/ethnicity-balance.md).
# Ethnicity balance
Study type
Availability
Screeners
true
Usability tests (auto-recruit)
true
Media surveys (auto-recruit)
true
Intercept studies
true
AI moderated studies (auto-recruit)
true
You may already be familiar with the [Participant balance](/recruit-participants/dscout-scout-panel/participant-balance.md) control which ensures a balanced sample across major demographics (i.e. age, ethnicity, gender) by limiting samples within each segment to 65%. The **Ethnicity Balance** feature allows you to further customize your participant pool by editing the maximum number of responses allowed per ethnicity group in a given screener, usability test, or media survey.
To access this feature, navigate to the **Overview** tab of your screener or **Screener** tab in your study, and toggle on the Balance feature.
In screeners, you can click Customize Ethnicity Balance to view the percentages grid and further customize.
This feature gives you more flexibility in creating a well-balanced mix of participants or narrowing your focus on one or more specific ethnic groups. For example, if you wanted to see no more than 25% of responses from participants who identify as White, you’d set the percentage next to “White” to be 25%. From there, you’d be able to customize the percentages for all other groups. Once the maximum percentage you set is reached, participants in that ethnicity group will no longer be able to view your screener or studies.
Similarly, if you wanted to see only responses from participants who identify as Black or African American, you’d set the percentage next to “Black or African American” to be 100%, and all other percentages to be 0%.
{% hint style="info" %}
**Note:** Sum of percentages must be equal to or greater than 100%.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.dscout.com/recruit-participants/dscout-scout-panel/ethnicity-balance.md?ask=&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 `automate deployments from our CI pipeline` 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.