> For the complete documentation index, see [llms.txt](https://docs.motus.org/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motus.org/en/project-management/collaborators.md).

# Collaborators

Collaborators are the glue that keeps Motus together. They are the researchers, landowners, and stakeholders that need to access the project's data.

## Adding a new collaborator to a project

1. Go to [**Manage Collaborators, Institutions, and Citations**](https://motus.org/data/project/users)
2. Below the table of collaborators, use the input field under **Add new collaborators** to search for the collaborator's name, username or email.
3. In the search results, click on the name of the collaborator you wish to add to your project.

{% hint style="warning" %}
Searching for collaborators by first name may not turn up any results.
{% endhint %}

## Citations

See [**Project Citations**.](https://docs.motus.org/en/project-management/citations.md#collaborator-citations)

## Project collaborator permissions

* Go to [**Manage Collaborators, Institutions, and Citations**](https://motus.org/data/project/users)
* Find the user you wish to revise in the collaborators table and then use the select options to modify their permissions. Permissions have three tiers -- 'update' (view and edit), 'read' (view only), and 'none' -- and include the following categories:
* **Project:** Anything related to project metadata (description, billing contact, etc.) and collaborator/citation management.
* **Tags:** tag deployment metadata.
* **Stations:** anything relating to station management including station deployment and landowner information.
* **Data:** access to detection data (via [**Motus R package**](https://motus.org/MotusRBook/)).

{% hint style="info" %}
Default permissions for a new collaborator is 'update' for all four categories.
{% endhint %}

![](https://2565212148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjf0K5m6GrB75xw7Xweac%2Fuploads%2Fgit-blob-861406626d3df301bb3dbab378f956cc04bddfca%2FManage%20Users%20-%20Permissions.png?alt=media)

## Removing a collaborator from a project

1. Go to [**Manage Collaborators, Institutions, and Citations**](https://motus.org/data/project/users)
2. Find the use you wish to remove in the collaborators table and then click on the![](https://2565212148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjf0K5m6GrB75xw7Xweac%2Fuploads%2Fgit-blob-58920847b2c322bcb11904b56134c80a83b3614d%2Fimage.png?alt=media)icon located at the end of the row.

![](https://2565212148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjf0K5m6GrB75xw7Xweac%2Fuploads%2Fgit-blob-f2fb5e8d1b83e733d8a8523c56ca6223ebaf3c19%2FManage%20Users%20-%20Delete.png?alt=media)


---

# 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.motus.org/en/project-management/collaborators.md?ask=<question>&goal=<user_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.
