> For the complete documentation index, see [llms.txt](https://support-en.braver.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support-en.braver.net/guides/for-healthcare-professionals/discussion-threads/find-closed-discussion-thread.md).
# Find a Closed Discussion Thread
{% hint style="info" %}
When a discussion thread is closed, it becomes an immutable artifact, but remains accessible and downloadable as PDF.
{% endhint %}
## Step-by-Step
{% stepper %}
{% step %}
#### This is the team box. Closed discussion threads can be recognized by the hook on the right side of the excerpt.
{% endstep %}
{% step %}
#### If you click on it, you see the mention *Collaboration was closed*.
{% endstep %}
{% step %}
#### You can also find closed discussion threads by opening a patient file.
{% endstep %}
{% step %}
#### Here, I still have access to closed threads outside the channel.
{% endstep %}
{% step %}
#### Always in the patient file, I can select *View details* in a care channel to find its closed discussion threads.
{% endstep %}
{% step %}
#### There is a closed thread in this care channel.
{% endstep %}
{% step %}
#### Finally, under Network tab, select one of your contacts to see active or closed discussions with them.
{% endstep %}
{% step %}
#### They are accessible here!
{% endstep %}
{% endstepper %}
---
# 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://support-en.braver.net/guides/for-healthcare-professionals/discussion-threads/find-closed-discussion-thread.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.
