> For the complete documentation index, see [llms.txt](https://academy.synap.ac/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.synap.ac/doc/users-and-groups/permissions/collaborators.md).
# Collaborators
Collaborators let educators share the content they’ve created with other educators, so they can work on it together with the same level of control.
Collaborators allow educators to give other educators (that they have permission to see) access to content they have created, allowing them to manage and edit that content as if they were the owner.
{% hint style="info" %}
Collaborators require Pro or higher plans
{% endhint %}
When a user creates content (such as an exam or library item), they automatically become the **owner**.
Owners:
* Have full control over the item
* Can edit, manage, and delete it
* Do **not** require additional permissions to manage their own content
This allows educators to independently create and manage their own work without needing elevated permissions.
{% hint style="info" %}
Admins and Managers never need to be Collaborators as they have the same ownership abilities as Educators on any content.
{% endhint %}
Adding other users in as Collaborators gives them the same level of access as owners to content. This means teams can manage their own content without having to have global permissions to be able to set specific permissions or having to have multiple specific permissions set on every exam or content their team makes. Meaning simpler permission set up for this usecase
Simple permissions set up for Educators to create and manage their own teams content without having access to everything or editing permissions
### When to use Collaborators
A typical setup is a team of educators who each manage their own content:
* Educators can create exams or library content independently
* They automatically have full control over what they create
* They can invite teammates as collaborators to help review or edit
This avoids the need to give educators higher-level permissions such as **“set permissions”**, while still enabling collaboration.
Collaborators are useful when:
* You want to **avoid over-permissioning users**
* Teams need to **work together on specific content**
* Access needs to be **temporary or limited in scope**
* You want to **keep global permissions simple and controlled**
## How to add Collaborators
From the library content or exam details page, educators will see who the owner is, as well as any current collaborators. Click to add a collaborator either individually or by group.
The only users who can add collaborators to specific content or exams are:
* Owners
* Other collaborators
* Admins / Managers
Users with edit access alone will not be able to add other educators to be collaborators.
Once added and changes saved, collaborators will see the item in their library and have full ownership access.
---
# 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://academy.synap.ac/doc/users-and-groups/permissions/collaborators.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.
