> 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/for-administrators/users.md).

# Users

A user can be invited into an organization as a [**professional**](#professional-user), [**administrative**](#administrative-user) user, or both.

{% hint style="info" %}
We do not refer to a patient or caregiver user as a user who is part of an organization.

This type of user only receives limited access to certain care channels. They do not appear anywhere else as users who can receive additional access from the organization.
{% endhint %}

Adding a user to an organization is done by inviting them into an [organizational unit](/for-administrators/organizational-units.md).

The first time they are invited in this manner into a given organization, they receive an email inviting them to accept the invitation (possibly by completing the creation of their account). If, subsequently, they are invited into another unit of the same organization, they will not need to do anything and will not receive an email invitation.

### Professional User

A user is considered "professional" if they have access to the Braver communication application to interact with other users using discussion threads and care channels.

To have this type of access on behalf of the organization, the user in question must be part of at least [one team](/for-administrators/teams.md) as a participant or team manager.

### Administrative User

A user is considered **administrative** (or simply an **administrator**) if they have access to the administrative console.

To have this type of access for a given organization, the user in question must have the *Admin* role for at least one of the organization's [organizational units](/for-administrators/organizational-units.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support-en.braver.net/for-administrators/users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.