> 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/getting-started/workspaces-and-projects/create-a-project-study-or-screener.md).
# Create a project, study, or screener
Whether you’re creating a new study, a screener to help recruit for that study, or a project to keep it all organized, here’s a quick guide to get you started.
## Create a project
Think of projects as folders to keep your research organized. You might need multiple studies or studies to get the insights you’re looking for, and you can keep them all together in a single project.
To create a project, click **New Project** in the top-right corner of the Dscout homepage.
Now, you’re taken to the blank project’s page where you can edit the project’s details, build studies and screeners, and invite project members.
{% hint style="success" %}
**Tip:** Give your project a descriptive title and quick description so any project members you invite have context around the project’s purpose. Don’t worry—your research participants won’t see either of these.
{% endhint %}
## Create a study
Studies are the heart of conducting research in Dscout. They’re how you build, manage, and field moderated and unmoderated studies. Once you’ve created a project, you can start creating studies.
**To create a study:**
{% stepper %}
{% step %}
Navigate to the project where you want your study to live.
{% endstep %}
{% step %}
Click the **Create study** button in the top-right corner of the page. The **Create something new** modal is displayed.
{% endstep %}
{% step %}
Select a study type from the following options:
* **Usability test:** Great for quickly validating and iterating with heat maps, task prompts, and more.
* **Media survey:** Great for capturing deep survey data with photos, videos, and more.
* **Diary study:** Great for exploring habits and behaviors over time through multiple activities.
* **Interviews:** Great for having moderated sessions with participants with automated transcripts, notes, and more.
* **Intercept study:** Great for gathering in-the-moment feedback from users of live websites.
* **AI moderated study (beta):** Great for gathering interview-style responses at scale.
{% endstep %}
{% step %}
Follow the prompts to set up your selected study.
{% endstep %}
{% endstepper %}
For more study type-specific help, check out the following articles:
* [Create a usability test](/usability-tests/create-a-usability-test.md).
* [Create a media survey](/media-surveys/create-a-media-survey.md).
* [Set up a diary study](/diary-studies/what-are-diary-studies-in-dscout/set-up-a-diary-study.md).
* [Create an interview study](/interview-studies/create-an-interview-study.md).
* [Create an intercept study](/intercept-studies/create-an-intercept-study.md).
* [AI moderated studies](/dscout-ai/dscout-ai-studio/ai-moderated-studies.md).
## Create a screener
Screeners are how you recruit participants to join your studies. You can create a public screener to recruit directly from Dscout’s pool of participants (known as Scouts) or a private screener which you can then share with whoever you want using a dedicated share link.
{% stepper %}
{% step %}
Navigate to the project where you want your screener to live.
{% endstep %}
{% step %}
Click the **Screeners** tab at the top of your project.
{% endstep %}
{% step %}
Click the **Create screener** button in the top-right corner of the page.
{% endstep %}
{% step %}
Follow the prompts to set up your screener.
{% endstep %}
{% endstepper %}
For more information on creating a screener, see [Set up a screener](/recruit-participants/what-are-dscout-screeners/set-up-a-screener.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://help.dscout.com/getting-started/workspaces-and-projects/create-a-project-study-or-screener.md?ask=&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.
