> 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/intercept-studies/manage-an-intercept-study/close-an-intercept-study.md).
# Close an intercept study
When you no longer want to receive new responses to your study, you can close it. Closing an intercept study prevents it from being displayed to new participants. (Participants who have already started their submissions will still be able to finish.)
{% hint style="info" %}
**Note:** Your study will close automatically when you reach your participant limit. However, you can close your study early by following the steps below.
{% endhint %}
{% stepper %}
{% step %}
Open your study in the browser.
{% endstep %}
{% step %}
Click **Close** in the top right corner of the builder. A confirmation modal is displayed.
{% endstep %}
{% step %}
Click **Close** to confirm.
{% endstep %}
{% endstepper %}
Now, your study is closed. Participants with in-progress submissions will be able to complete the study, but new participants will not be able to begin. If you want to re-launch a study after it’s been closed, you can edit it and then re-launch. For more information, see [Edit a launched screener or study](/study-basics/edit-close-or-relaunch-studies/edit-a-launched-screener-or-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/intercept-studies/manage-an-intercept-study/close-an-intercept-study.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.