> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/basespace/collaborate/share-with-collaborators/manage-collaborator-access.md).

# Manage Collaborator Access

Use the Send Invitation option to manage collaborator permissions. You can review the list of collaborators, change the access level for a project, or revoke access to a run or project.

1. Select the shared project or run.
2. Select Share, and then select Send Invitation.
3. In the Collaborator Settings section of the Share dialog, change or revoke collaborator access.
4. Select Save Settings.

{% hint style="info" %}
The collaborator list uses the email address of the personal account or workgroup owner. Because users can accept shares on behalf of workgroups, the listed collaborator might not be the same as the user who received the invitation to share.
{% endhint %}

{% hint style="info" %}
Runs and projects have separate permissions. When you change access to a project, access to shared runs is not automatically changed.
{% 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://help.bioinsight.illumina.com/basespace/collaborate/share-with-collaborators/manage-collaborator-access.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.