> 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/diary-studies/manage-a-diary-study/launch-a-diary-study.md).

# Launch a diary study

When you're ready to open your study to participants, you'll launch it from the builder.

**To launch your diary study:**

{% stepper %}
{% step %}
Open your study in the builder.
{% endstep %}

{% step %}
Click **Launch study** in the bottom right corner. A study summary modal is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FARL4LPPPyudEUnvgtf0p%2FLaunch_diary.jpg?alt=media&amp;token=0575b2aa-9245-43ef-9b29-d18ab41709f3" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** If you still have unmet requirements, you'll see a **Before you launch** button with a count instead. Open it to see what needs your attention, and resolve each item to launch your study.
{% endhint %}
{% endstep %}

{% step %}
Confirm the displayed summary of your study. If anything looks off, click **Cancel** and make the necessary adjustments to your study.
{% endstep %}

{% step %}
Click **Launch study**.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FpTmI55qxdvGGwRRAtpCR%2FLaunch_diary%20(1).jpg?alt=media&amp;token=6949353d-96f9-488b-99a7-7797f05fe788" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

Now, your study is launched—congrats! You're one step closer to getting valuable insights. For information on what happens next, see the section below.

## What happens when I launch my study?

Launching your study results in slightly different behavior depending on how you recruit participants:

* **Adding participants from a screener or previous study:** Participants you've added from a Dscout screener or another Dscout study automatically receive an email inviting them to your study.
* **Inviting your own participants by email:** Participants you've added manually (by name and email) automatically receive an email inviting them to your study.
* **Using a study webpage:** If you're bringing your own participants using a study webpage, launching your study activates the webpage. You can then share the webpage link with anyone you want to invite, and they'll be able to sign up for your study. For more information, see [Diary webpages](/diary-studies/create-a-diary-study/diary-webpages.md).

Need to invite more participants after launch? For more information, see [Invite participants to a diary study](/diary-studies/manage-a-diary-study/invite-participants-to-a-diary-study.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/diary-studies/manage-a-diary-study/launch-a-diary-study.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.
