> 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/filter-by-participation.md).

# Filter by participation

Private Panels only marks panelists as having participated in a study if they have a **Completed** or **Scheduled** status within a study, or if they have a scheduled session or have been assigned an interview spot. You can follow our [Updating Respondent Status](/private-panels/studies/update-respondent-status.md) guide to update a panelist's status, while you can read our [Study Scheduling](/private-panels/studies/private-panels-study-scheduling.md) guide for more details on scheduling.

If you'd like to view which panelists have, or do not have, past participation, go to **Panel Panelists**. Then, follow the steps below:

{% stepper %}
{% step %}
Click the **+ Add Filter** button. If you'd like to view those with past participation, select **Scheduled In Study** from the drop-down options. Select **Not Scheduled In Study** instead if you'd like to view those without past participation.
{% endstep %}

{% step %}
A drop-down list will appear containing all studies. Tick the checkboxes beside the studies that you'd like to use for the filter. The filter condition will update based on your selection.
{% endstep %}

{% step %}
After filtering, only those that fit the filter conditions will be listed in **Panel Panelists**.

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

{% 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/filter-by-participation.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.