> 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/get-started/quickstart-guide.md).

# Quickstart guide

Welcome to Private Panels, your one-stop solution for panel management. With Private Panels, you can build your own participant pool, run studies, and more. But first, let’s run through a few steps to get you (and your team!) up and running.

{% stepper %}
{% step %}

## Set up your account

If you’re new to Private Panels, the first thing to do is create your account. Whether you’ve been invited by an admin or need to create your account from scratch, see [sign in to private panels](/private-panels/get-started/sign-in-to-private-panels.md) for more information.

If you’re an admin, you’ll also want to invite the members of your team who should have Private Panels access. For more information, see [Invite users to Private Panels](/private-panels/organization-settings/invite-users-to-private-panels.md).
{% endstep %}

{% step %}

## Customize your communications

Private Panels lets you customize branding elements, email sender information, and more to offer your panelists a consistent, on-brand experience. Here are some useful resources to help:

* [Private Panels custom branding](/private-panels/organization-settings/custom-branding.md).
* [Custom domain for emails](/private-panels/organization-settings/custom-domain-for-emails.md).
  {% endstep %}

{% step %}

## Connect to your other tools

With integrations, you can supercharge your Private Panels workflows using tools you already have. For more information on what’s available, see [Integrations](/private-panels/get-started/welcome-to-private-panels.md).
{% endstep %}

{% step %}

## Understand the panel structure

Before you can build out your panels, it’s important to understand what components power them. Here’s a quick breakdown:

* **Panel properties:** Individual pieces of data you want to store about each of your panelists. If you think about Private Panels as a spreadsheet, panel properties are your columns, and panelists are your rows. For more information, see [panel properties](/private-panels/panel-management/panel-properties.md).
* **Multiple panels:** Most teams start with one panel. If you have distinct audiences, for example consumers vs. enterprise buyers, you can plan separate panels. For more information, see [multiple panels](/private-panels/panel-management/multiple-panels.md).
  {% endstep %}

{% step %}

## Add panelists (or recruit them)

Once you’ve set up your panels, you can add your panelists. Whether you already have panelists or want to recruit them, Private Panels offers two main options:

* **Import panelists** via CSV file, Salesforce, or API. For more information, see [create upload and manage private panels panelists](/private-panels/panel-management/create-upload-and-manage-panelists.md).
* Recruit using a **panel sign-up form**. For more information, see [panel sign up forms](/private-panels/panel-management/panel-sign-up-forms.md).
  {% endstep %}

{% step %}

## Run a study

Once you’ve worked through the above steps, you’re ready to gather insights using a Private Panels study. For more information, see [create a private panels study](/private-panels/studies/create-a-private-panels-study.md). If you also have access to the core Dscout platform, you can add panelists directly to a Dscout study. For more information, see [add participants to a dscout study from private panels](/private-panels/get-started/add-panelists-to-a-dscout-study-from-private-panels.md).
{% endstep %}
{% endstepper %}


---

# 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/get-started/quickstart-guide.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.