> 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/screeners/survey-status.md).

# Survey status

There are four visibility settings that can be updated in the **Screener Settings** **Who can take the screener** section.

* **Study Participants:** only respondents who have been added to this study can answer the screener.
* **Anyone:** anyone with the public link can answer this screener.
* **Private:** only logged-in admins can answer this screener (e.g. used for internal phone screeners).
* **Nobody:** screener is no longer accepting responses.

![](/files/3a02110e36a8b5e3c53756a866aaa94143930e70)

## Get a shareable link

To get a public survey link (e.g. to share on social media), you can set **"Who can take the screener?"** to Anyone. You must ask for the respondent's email address, and save this to the panel.

To do this, either use the **Contact Info** helper to generate the correct questions (First Name, Last Name, and Phone Number), or scroll down to the section below "How to configure email question".

![](/files/5ffabf96b883b5caf42d55fee4446d62e8abbf9a)

## How to configure email question

Create your own "Email" question like this:

{% stepper %}
{% step %}
Create a **Short Answer** element in your screener asking for their "Email"
{% endstep %}

{% step %}
Mark it as **Required**
{% endstep %}

{% step %}
Enable **Two-way panel property sync** and link it to **Email**
{% endstep %}
{% endstepper %}

![](/files/92f4970500d433d25af91fc8bd45fa7f26237383)

{% 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 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/private-panels/screeners/survey-status.md?ask=<question>&goal=<endgoal>
```

`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.