> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/survey-design-and-deployment/participant-directory-overview/use-a-participant-list-in-a-survey-quick-start.md).

# Use a Participant List in a Survey - Quick Start

Connect a participant list to a new survey, either everyone on it or a filtered group, so the survey's participants come from Participant Directory and stay current while it is open.

{% hint style="info" %}
**Who can do this.** Site Admins and Report Viewers holding a Survey Creator license can connect a list to a survey.
{% endhint %}

***

## Connect a list workflow

### Step 1: Open the survey's participants

1. Navigate to **Surveys** and open a new survey.
2. Select **Participants**. Compass asks where the participants come from.
3. Select **Add from directory**.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FajJGWBKGE1q29K2UEqnM%2FScreenshot%2014%20participant%20source%20dialog%20with%20Add%20from%20directory%20and%20Manual%20Import.png?alt=media&amp;token=b793fabe-4ce8-49ac-a6f3-9427efa43241" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**The choice is permanent for this survey.** A survey uses either a list or its own file, never both, and you cannot switch later. Select **Manual import** instead if this survey needs its own file.
{% endhint %}

### Step 2: Select a list

1. Select the list you want. A survey uses one list.

### Step 3: Select who takes part

1. Under **How much of this list?**, select **Everyone on this list**, or select **Filter to a group** to narrow it.
2. To filter, select **Set filter**, build the filter, for example Department is Finance, and select **Apply filter**.
3. Select **Save selection**.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FgcBVWELM2UXrAjvwzuUO%2FScreenshot%2015%20list%20and%20filter%20selection%20for%20the%20survey.png?alt=media&amp;token=f1b502bc-3f60-46be-ba64-7d6af6ef7a69" alt=""><figcaption></figcaption></figure>

### Step 4: Check the participants

1. Review the survey's participants. Columns that come from the list are marked **Directory** and are read-only, with a banner explaining that they are edited in Participant Directory.
2. Continue setting up and scheduling your survey as usual.

***

## Ready to launch

1. Schedule your invitations. See [Scheduling Emails - Quick Start](/knowledge-base/survey-design-and-deployment/scheduling-emails-quick-start.md).
2. Keep the list current in Participant Directory. The survey picks up changes until it closes for the first time.

***

## Related articles

* [Surveys Using a Participant List - Complete Guide](/knowledge-base/survey-design-and-deployment/participant-directory-overview/use-a-participant-list-in-a-survey-quick-start/surveys-using-a-participant-list-complete-guide.md)
* [Set Up a Participant List - Quick Start](/knowledge-base/survey-design-and-deployment/participant-directory-overview/set-up-a-participant-list-quick-start.md)
* [Import Participants](/knowledge-base/survey-design-and-deployment/import-participants.md)


---

# 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://docs.talentmap.com/knowledge-base/survey-design-and-deployment/participant-directory-overview/use-a-participant-list-in-a-survey-quick-start.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.