> 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/public-private-panels-screener-links.md).

# Public Private Panels screener links

## How to get a public shareable link

{% stepper %}
{% step %}
Navigate to **Screener Screener Settings**.
{% endstep %}

{% step %}
Set **Who can take the screener?** to **Anyone**.

Your survey must ask for the respondent's email address. The question must have **Two-way sync** enabled. This question must be asked **before** any disqualifying logic. This is how an answer will be associated with a panelist.

To do this easily, either use the **Contact Info** helper to generate the correct questions, or scroll down to the section below.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/pyNcOrvB7SJn1GLWQsMP/37073086617492)
{% endstep %}

{% step %}
Then you'll be able to see the **Public Link**.

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

## 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**.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/VV8Pd7YfcgG9vWZWbq3h/37073086619284)
{% 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/screeners/public-private-panels-screener-links.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.