> 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/create-non-clinical-discussion-thread.md).
# Create a New Non-Clinical Discussion Thread
## Step-by-Step
* [Scenario 1: Add one or more participants](#scenario-1-add-one-or-more-participants)
* [Scenario 2: Add one or more teams](#scenario-2-add-one-or-more-teams)
* [Another way to create a non-clinical discussion thread](#another-way-to-create-a-non-clinical-discussion-thread)
## Scenario 1: Add one or more participants
{% stepper %}
{% step %}
**Go to the *****Home***** page.**
{% endstep %}
{% step %}
**Select the bubble icon at the bottom of the page.**
{% endstep %}
{% step %}
**Choose *****Non-clinical thread*****.**
{% endstep %}
{% step %}
**In the composition menu:**
1. **Enter a title for your message.**
2. **Write the message content.**
3. **Select *****Attachments***** to add files if needed.**
4. **Set the priority to urgent if needed.**
5. **Click *****Next***** to go to the second composition page.**
{% endstep %}
{% step %}
**Click *****Add a participant*****.**
{% endstep %}
{% step %}
1. **Use the search bar to find the participants you want.**
2. **Click the name of the person you want to add.**
{% hint style="info" %}
To add a team, see [***Scenario 2: Add one or more teams***](#scenario-2-add-one-or-more-teams) below.
{% endhint %}
{% endstep %}
{% step %}
**After selecting the participant, click *****Add to the discussion*****.**
{% endstep %}
{% step %}
**Click *****Send***** at the bottom of the page.**
{% endstep %}
{% endstepper %}
{% hint style="success" %}
**Where to Find Them:**
* *Non-clinical threads* are accessible from the *Home* page. They are the ones not linked to a purple patient file (see image).
* You can also find *Non-clinical threads* under the *Network* page by selecting one of your collaborators for this thread.
{% endhint %}
## **Scenario 2: Add one or more teams**
{% stepper %}
{% step %}
**In step 6 of Scenario 1, click the workplace where your team is located:**
1. **Use the search bar to find the desired workplace.**
2. **Click the name of the workplace where the team you want to add is located.**
{% endstep %}
{% step %}
**After selecting the workplace, click *****Add to the discussion*****.**
{% endstep %}
{% step %}
**Click the name of the team you want to add.**
{% endstep %}
{% step %}
**Click *****Send***** at the bottom of the page.**
{% endstep %}
{% endstepper %}
## **Another way to create a non-clinical discussion thread**
1\) In the **Network** tab, 2) select your contact and 3) click **New thread**.
---
# 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/create-non-clinical-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.
