> For the complete documentation index, see [llms.txt](https://docs.pulselabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulselabs.ai/getting-started/project-setup-and-workflow.md).

# Projects

### What is a project?

A project is a container for a single research effort. It holds your data capture methods (surveys, evaluations, etc.), your participant pool, and your research team. Everything related to a study lives inside one project.

### Creating a project

1. From the sidebar, select **Projects**, then **Add Project**.
2. Enter the **name** — A clear, descriptive name (visible to your team and optionally to participants).
3. Enter the **Description** — What the study is about.

Your project starts in **Hidden** status — only you can see it until you share it.

### Project dashboard

The project dashboard has three main tabs.

#### Data tab

This tab is where your capture methods live. You'll see cards for each survey or evaluation you've added. From here you can:

* **See status at a glance** — Each card shows Draft, Active, or Completed status
* **Add a new capture method** — Select Add Capture Series and then choose Survey or Evaluation
* **Open an existing one** — Select a card to go to that method's dashboard.

If your project is empty, a **Next Steps** page guides you through setup.

#### Recruitment tab

Shows participants who have been invited to your project, with the number of participants and their current funnel status (recruited, verified, enrolled). From here you can:

* **Add participants** — By email, CSV upload, or from the Pulse Voices panel.
* **View participant status** — See where each person is in the verification process.
* **Manage invitations** — Resend invites or remove participants.

#### Enrolled tab

Shows participants who have completed all verification steps and are ready to participate. This is your active participant pool.

### Add a capture method

To add a method, go to the **Data** tab and select **Add Capture Series**.

A single project can contain multiple capture methods of any type. Combinations of capture methods could include:

* **Screener survey** — Qualify participants via survey, then send invitations to participate to those who passed the screener.
* **Survey + Evaluation** — Collect self-reported preferences, then observe actual behavior.
* **Multiple evaluations** — Test different prototypes with the same participant pool.

<table data-header-hidden><thead><tr><th width="154"></th><th></th></tr></thead><tbody><tr><td><strong>Method</strong></td><td><strong>Example</strong></td></tr><tr><td><a href="/pages/WvZxcDyWixjoTQmUGpEA">Survey</a></td><td>Quantitative feedback, user attitudes and preferences, running large-sample data</td></tr><tr><td><a href="/pages/Vbmi6UJKzQ2oKOggH59p">Evaluation</a></td><td>Unmoderated usability testing, longitudinal studies, task completion analysis, behavioral observation</td></tr></tbody></table>

### Building your team

Use the **Share** button to invite members to collaborate on your project:

1. Search for workspace members by name or email.
2. Assign a role: **Manager, Editor,** or **Viewer.**
3. They'll receive an invitation and can access the project immediately.

You can add team members at any time.

### Pulse Voices panel settings

If you're recruiting from the Pulse Voices panel, you can configure your project’s settings to make your project discoverable by the entire panel:

* **Visibility** — Hidden (invite-only) or Open (discoverable).
* **Project image** — Upload your own, choose stock, or generate with AI.
* **Participant-facing description** — What potential participants see when browsing
* **Tags** — Help participants find your study by topic.
* **Compensation and timeline** — Show expected pay and time commitment.
* **Branding** — Choose whether your organization name displays.

These settings are specific only to the participants in the Pulse Voices panel and the public participant marketing page if used. Your team's view is unchanged. For additional information on marketing your study to our Pulse Voices panel, go to \[insert link].

### Project lifecycle

<table data-header-hidden><thead><tr><th width="114.79998779296875"></th><th></th></tr></thead><tbody><tr><td><strong>Status</strong></td><td><strong>Meaning</strong></td></tr><tr><td>Draft</td><td>Setup phase. Capture methods can be configured but haven't been launched.</td></tr><tr><td>Active</td><td>At least one capture method is live and collecting data.</td></tr><tr><td>Archived</td><td>Study complete. Data is preserved but no new collection happens.</td></tr></tbody></table>

You can filter your projects list by status and sort by last modified date. Toggle between grid and list views using the view switcher.

### Tips

* **One study, one project** — Don't mix unrelated studies. The shared participant pool only makes sense when everything is part of the same research.
* **Name clearly** — Use names your team will recognize months later. Include the study topic or client name.
* **Start with capture methods** — Set up surveys or evaluations before adding participants, so the experience is ready when they arrive.
* **Use Draft mode** — Review and test your setup before launching to participants.

***

<br>

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pulselabs.ai/getting-started/project-setup-and-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
