> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/workbench/variant-interpreter/workspaces-and-roles.md).

# Workspaces & roles

A **workspace** is the environment you select after logging in. It is the container for everything you work with — storage accounts, samples, workflow runs, analyses, reports, and the people who can see them. You only ever see the data in the workspace you're currently in, and your **role** in that workspace decides what you can do.

## Selecting and switching workspaces

Your active workspace is shown in the user menu in the top navigation. Open the menu to switch to another workspace you belong to. Switching reloads the Data Page for the newly selected workspace.

If a sample you expect isn't listed, first confirm you're in the right workspace.

## When you have no workspace yet

If your account doesn't belong to any workspace, you land on a welcome screen instead of the Data Page. What it offers depends on your account:

* If you're allowed to create workspaces, it shows a **Create Workspace** action. Give the workspace a name and an optional description.
* Otherwise it asks you to have an administrator invite you to an existing workspace.

## Members and invitations

Workspace administrators manage membership from **Workspace settings → Members**:

* **Invite** one or more people by email address, assigning them a role. Each invitee's result is reported back (added, already a member, or not yet registered).
* **Change a member's role** or **remove** a member from the row actions.

## Roles and what they can do

Every member has one of three roles. Each role grants a fixed set of capabilities, and those capabilities control access to features across the interpreter — if you don't have a capability, its controls are hidden or disabled rather than failing when you click them.

| Role            | Intended for                                                                                       |
| --------------- | -------------------------------------------------------------------------------------------------- |
| **Viewer**      | Read-only access — review samples and analyses without changing them.                              |
| **Contributor** | Day-to-day interpretation — manage samples, run analyses, and classify variants.                   |
| **Admin**       | Full control — everything a contributor can do, plus workspace administration and report sign-off. |

The capabilities that matter most during interpretation:

| Capability            | What it allows                                         | Typical role       |
| --------------------- | ------------------------------------------------------ | ------------------ |
| **Manage Samples**    | Add and edit samples and their metadata.               | Contributor, Admin |
| **Run Workflows**     | Launch and re-run analyses.                            | Contributor, Admin |
| **Classify Variants** | Apply ACMG/AMP classifications to variants.            | Contributor, Admin |
| **Sign Off Reports**  | Approve, reopen, and close (release) clinical reports. | Admin only         |
| **Manage Users**      | Invite and remove members, assign roles.               | Admin              |
| **Manage Workspace**  | Rename, edit, or delete the workspace.                 | Admin              |

{% hint style="info" %}
Report sign-off is deliberately admin-only. Contributors can draft a report and submit it for review, but only an admin can approve and release it. See [Generating a report](/products/workbench/variant-interpreter/generating-a-report.md).
{% endhint %}

## Workspace settings

Administrators reach workspace administration from **Workspace settings**:

* **Details** — rename the workspace or edit its description.
* **Roles & permissions** — review the full capability matrix for each role.
* **Delete** — permanently remove the workspace and its configuration.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omics.ai/products/workbench/variant-interpreter/workspaces-and-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.