> 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/ai-moderated-studies/manage-an-ai-moderated-study/close-an-ai-moderated-study.md).
# Close an AI moderated study
Your study closes automatically when you reach your participant limit (required when auto-recruiting, optional when inviting your own participants). You can also close it early if you no longer want new responses. Closing prevents new participants from starting, but anyone who has already started can still finish.
{% hint style="warning" %}
**Warning:** You can't reopen an AI moderated study once it's been closed. Only close your study if you're sure no more responses are needed.
{% endhint %}
**To close an AI moderated study:**
{% stepper %}
{% step %}
Open your study in the builder.
{% endstep %}
{% step %}
Click **Close** in the top-right corner. A confirmation modal is displayed.
{% endstep %}
{% step %}
Click **Close** to confirm.
{% endstep %}
{% endstepper %}
Now, your study is closed. Participants with in-progress submissions can finish, but new participants can't begin.
---
# 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/ai-moderated-studies/manage-an-ai-moderated-study/close-an-ai-moderated-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.
.jpg?alt=media&token=ffa3acf0-5eca-4f08-bd9f-0a4e94a9fab4)