> 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/studies/delete-screener-response.md).

# Delete screener response

You can ensure the integrity of your study by deleting responses that don't add value to it or came from questionable sources. For example, screener responses from [duplicate respondents (by IP)](/private-panels/studies/duplicate-ip-protection.md).

To delete screener responses within a study:

{% stepper %}
{% step %}
Select the panelists whose responses you'd like to delete.
{% endstep %}

{% step %}
Click the **Bulk Actions** drop-down button.
{% endstep %}

{% step %}
From the drop-down options, hover your mouse cursor over **Delete responses**. The list of screeners for that study will pop-up as a list.
{% endstep %}

{% step %}
Select the screener where you'd like to delete the responses from.
{% endstep %}

{% step %}
Confirm the action by clicking the **OK** button on the pop-up dialog box at the top of the screen.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/RxVG9Dd9MkVPGeWa34r4/38054285791508)
{% endstep %}
{% endstepper %}

{% hint style="info" %}
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/studies/delete-screener-response.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.