> 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/icm/studies/inviting-study-collaborators.md). # Inviting Study Collaborators ## What is study collaboration? Study owners can invite people or workgroups to a study. This avoids duplicating data or granting broad workgroup membership. Each invitation carries an [access level](#access-levels) that governs what the invited party can do in the study. {% hint style="warning" %} Study invitations do not grant access to sample files in BioInsight Platform Core (Core) Projects. Core manages this access independently. To access sample files, collaborators need access to the relevant Core Project. Without it, errors may be encountered when: * Creating an analysis from study samples * Exporting or using [Share Analysis](/icm/analyses/analysis-functionality/share-analysis.md) {% endhint %} ### Who uses it? * **Owner —** invites collaborators and manages invitations from the study's **Team** tab. * **Person —** receives a direct invitation and accepts it through the email link. * **Workgroup —** receives an invitation directly. A member accepts it for the workgroup. * **Workgroup by proxy —** uses a designated person to accept an invitation for a workgroup. {% hint style="warning" %} After inviting a workgroup by proxy, check that the correct workgroups are listed. Revoke and reinvite if needed. {% endhint %} ## Access levels * **Owner —** the creator * **Administrator —** can view the study and manage invitations. * **Contributor —** can view the study and import or share analyses. * **Viewer —** read-only access to the study and its contents ### Actions for the study based on access level These actions apply to study data, samples, sample groups, and analyses.

Action	Owner / Creator	Administrator	Contributor	Viewer
Study appears in My studies	✅
Study appears in Shared with me		✅	✅	✅
Open / view the study	✅	✅	✅	✅
View samples, sample groups, analyses	✅	✅	✅	✅
Update study metadata (name, description, settings)	✅
Import data into the study (from BioInsights Connected Core)	✅
Add samples to the study (from Global Samples)	✅
Remove samples from the study	✅
Create sample groups	✅
Modify sample groups	✅
Delete sample groups	✅
Create analyses	✅
Launch analyses	✅
Modify / abort analyses	✅
Delete analyses	✅
Import / Share Analysis	✅	✅	✅
Delete the study	✅

### Invitation and team actions by access level These actions apply to the **Team** tab and study invitations. Owners cannot invite their own context.

Actions	Owner / Creator	Administrator	Contributor	Viewer
See the Team tab in study detail	✅	✅
List invitations for the study	✅	✅
Create a new invitation	✅	✅
Revoke an invitation	✅	✅
Modify an invitation's access level	✅	✅
Resend an invitation email	✅	✅
View a pending invitation	✅	✅	✅	✅
Accept / decline a pending invitation	✅	✅	✅	✅

{% hint style="warning" %} Privileges here do not override subscription tiers. A Contributor with an [Illumina BioInsight Platform (formerly Connected Software) Basic subscription](https://help.connected.illumina.com/icm#illumina-bioinsight-platform-formerly-connected-software-basic) is still a Contributor in Connected Multiomics; but downstream analysis options will be restricted at the Basic level (e.g. no new tasks can be run). {% endhint %} ## Invite team members From a study: * Click the **Team** tab * Click

Within a study, use the **Team** tab to select **Invite members**

* Choose an invitation type: ### Person * Enter an **email address** * Choose the [Access level](#access-levels) as Viewer, Contributor, or Administrator

### Workgroup * Select a **Workgroup** that you are a member of * Choose the [Access level](#access-levels) as Viewer, Contributor, or Administrator

### Workgroup by proxy * Enter one **email address** for the person to accept for their workgroup * Choose the [Access level](#access-levels) as Viewer, Contributor, or Administrator

## Team The invitation appears in the **Team** tab. It includes the recipient, invitation type, access level, status, and [actions](#resend-or-revoke-access).

The invitation will show in the **Team** tab with extra details and actions

The owner receives an email when the invitee accepts the invitation. ## Resend or revoke access From **Actions**, select

**Resend**,

**Change access level**, or

**Revoke**.

Invitation changes appear in the **Status** and **Actions** columns. If access is revoked, the invitee receives an email confirming the removal. ## Receive invitations Invitees receive an email and an in-app notification. They can view the invitation and accept the study share.

If the button does not work, copy the included link into a browser. ### Shared with me The **Shared with me** tab shows accepted shared studies.

**Shared with me** shows the studies that have been shared and accepted

--- # 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/icm/studies/inviting-study-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.