> 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/private-panels/panel-management/blocklist.md).

# Blocklist

If you want to block a participant from participating in your panel/studies, you can now add them to the Blocklist. This will flag the participant in question, and prevent that participant from being messaged or completing screeners.

When a participant is added to the blocklist, you will notice this in two areas. The first is the Blocklist panel property:

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/6tWuM4BSRjp2R4ajeKRb/37037703824148)

The second is on the panelist message tab:

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/H9uNPdTE4jqgUSU1yfsb/37037703824404)

Additionally, the panelist will not be notified that they are blocklisted. This is to prevent the panelist from knowing that their account cannot complete screeners.

If a panelist has incorrectly been assigned to the Blocklist, you can set the blocklist panel property to False, and the participant can complete screeners and be messaged as before.

{% hint style="info" %}
**Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact <support@dscout.com>.
{% 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/private-panels/panel-management/blocklist.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 `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.