> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/campaigns/campaign/panels.md).

# Panel Members Distribution

## 👪 **What is a panel members distribution ?**

The panel members distribution is a powerful feature that will use the [panelists](/panels/panelists.md) of your [panels](/panels.md) as recipients. 

This way you can for example create a [panel ](/panels.md)that acts as a contact list and send out invitations to members of that panel or you could link a panel to one an existing SQL table that has contacts and re-use that existing information to send out your invitations.

{% hint style="info" %}
Panelist attributes can be pipe anywhere in the invitation text using the `++yourpanelattributepipe++` tag that can be found in the panel attribute settings page. 
{% endhint %}

## 🚀 **Panel Campaign Setup** 

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBNJL0kRDaza4HuqAfv%2F-MBNKlV3JyTCrqsC5rf-%2Fimage.png?alt=media\&token=8da49934-2f67-4922-8533-44d1876faa85)

1. Select the panel having the panelists that will be used as recipients.
2. Select the attribute that will be used as recipient value (email / phone) for your campaign.
3. Send your invitations to all panel members or only to a few selected one. 

{% hint style="warning" %}
While automatically enabled by ngSurvey during the campaign launch its important to note that the i[nvitation code security item](/form-management/security/security-items/invitation-code.md) must be enabled on your survey to validate the invitation codes and to link the email to the respondent.
{% 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://docs.ngsurvey.com/form-management/campaigns/campaign/panels.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.