> 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/mark-a-project-as-complete.md).

# Mark a project as complete

When all research in a project has been completed, you can mark it as complete to close it.

**When a project is marked as complete:**

* All studies and screeners within the project are closed.
* The project is moved to the **Completed** view of your Dscout account and cannot be moved back.
* Studies and screeners within the project can no longer be duplicated or moved out of the project.
* If automatic project deletion is enabled, the project is queued for deletion according to your organization’s settings. For more information, see [Project data deletion](/account-management/organization-account-settings/project-data-deletion.md).

{% stepper %}
{% step %}
On the **Projects** page, click the three-dot icon on the project you want to complete.
{% endstep %}

{% step %}
Select **Complete project**. A confirmation modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5WzCx6nDFHoeD0SUC0pE/41597991022612)
{% endstep %}

{% step %}
Click **Complete project** to confirm.
{% endstep %}
{% endstepper %}

Now, any open studies or screeners in your project are closed and the project is moved to the **Completed** view of your Dscout account.

**To view completed projects**, click **Completed** in the top right corner of the Projects page:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/n6M46ugXokeUWyn4ci5w/41597991023636)

{% hint style="info" %}
Projects will only remain in your **Completed** view in accordance with your organization’s project data deletion protocol. For more information, see [Project data deletion](/account-management/organization-account-settings/project-data-deletion.md).
{% endhint %}


---

# 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/mark-a-project-as-complete.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.