> 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/panels/panel-views.md).

# Panel Views

## 👀 What are panel views ?

Panel views are subsets of your [panel members](/panels/panelists.md) that you can define using a set of [rules](/form-management/form-designer/condition-rules/conditions-rules.md). Once you have created a subset of your panelists using a panel view you could reuse it for example to create [targeted mailing invitations](/form-management/campaigns/campaign/panels.md)  or to [filter](/form-management/reports/filters.md) out your survey results based on the [panelists](/panels/panelists.md) that are part of the view.

## ➕ Adding a panel view

To add a new panel view click on the **New panel view button** of the **Views** section.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MC685jvWGwCt8CsmxTT%2F-MC68jaADX6zmqmU3IHy%2Fimage.png?alt=media\&token=65ab1751-b234-4135-ac2a-862869785b79)

1. Total panelist count that are part of the view. You may also view the panelists of this view by clicking on it.
2. [**Condition rules**](/form-management/form-designer/condition-rules/conditions-rules.md) defining what panelist should be included in this view.

## 🚀 Panel view actions

Using the 3 dots button you can trigger some quick actions to manage your panel view.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MC6939MFUSWdhxZpE6X%2F-MC697XuQWjpj_Auuz_0%2Fimage.png?alt=media\&token=f42acf45-4221-4160-b25a-df723e6c60dc)

* **`Delete`** the panel view. Deleting a view will not delete any panelists from it.


---

# 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/panels/panel-views.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.