> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/openbrim/getting-started/navigation-within-openbrimapp/projects/projects-users.md).
# Projects Users
By default, projects are only visible to the user who created them. Grant access to other users as needed.
***
## Managing Access
Click **Users** in the left sidebar to view and manage project access.
Project users panel
### User Actions
| Action | How |
| ------------------- | ------------------------------------------------------ |
| **Add user** | Click the plus icon and enter the user's email address |
| **Set permissions** | Choose Read Only, Write, or Admin access |
| **Remove user** | Click the delete icon next to the user |
Adding and managing project users
***
## Permission Levels
| Level | Can View | Can Edit | Can Manage Users |
| ------------- | -------- | -------- | ---------------- |
| **Read Only** | Yes | No | No |
| **Write** | Yes | Yes | No |
| **Admin** | Yes | Yes | Yes |
***
## Real-Time Collaboration
OpenBrIM supports simultaneous collaboration using WebSocket technology. When one user makes changes, all other users with access see updates automatically. Changes are recorded in the revision history.
{% hint style="info" %}
**Working on different scenarios:** If you want to explore different options without affecting your colleague's work, duplicate the project. Each copy has its own independent revision history.
{% endhint %}
***
## Sharing Options
{% hint style="warning" %}
**Understanding share types:**
* **Project link:** Recipients with workspace access see the current project state (view-only unless given write access)
* **Revision link:** Recipients see only that specific snapshot, not subsequent changes
* **User access:** Added users can view full revision history regardless of their permission level
{% 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://docs.openbrim.org/openbrim/getting-started/navigation-within-openbrimapp/projects/projects-users.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.
