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

# Members and roles

*What you'll get: who can do what in a workspace, and how to invite, change and remove people.*

Everyone in a workspace has one of three roles: **Owner**, **Admin** or **Member**. There is no guest role: to work in a workspace, someone has to be a member of it.

To see who's in a workspace, switch to it and click **Members** in the sidebar (`/w/<workspace-url>/members`). Everyone in the workspace can see the list. Owners and admins also invite and manage people there.

<figure><img src="https://3806122466-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk3DfNQKoMy1JXdaDLvpG%2Fuploads%2Fgit-blob-8b270bf6f19dfabf98e6ba5831093d4da52a4aad%2Fws-members-page.png?alt=media" alt="The Members page of a workspace: active members with their roles, two pending invitations, and the Invite people button"><figcaption><p>The <strong>Members</strong> page. Pending invitations are listed with the members.</p></figcaption></figure>

## What each role can do

|                                                                                               | Owner | Admin | Member |
| --------------------------------------------------------------------------------------------- | :---: | :---: | :----: |
| Upload, create projects and run analyses, on the workspace's credits                          |   ✓   |   ✓   |    ✓   |
| See items shared with everyone in the workspace                                               |   ✓   |   ✓   |    ✓   |
| Share what they created                                                                       |   ✓   |   ✓   |    ✓   |
| See the member list                                                                           |   ✓   |   ✓   |    ✓   |
| See the workspace's credits and storage, and their own spending                               |   ✓   |   ✓   |    ✓   |
| See everyone's spending                                                                       |   ✓   |   ✓   |    —   |
| Invite people, change roles, deactivate and reactivate members                                |   ✓   |   ✓   |    —   |
| Change workspace settings and see the audit log                                               |   ✓   |   ✓   |    —   |
| Change who can see any item they can see                                                      |   ✓   |   ✓   |    —   |
| Publish the workspace's models to the public model catalogue                                  |   ✓   |   ✓   |    —   |
| Allow, or turn off, sending target sequences out for structure prediction (**Data handling**) |   ✓   |   ✓   |    —   |
| Buy credits and storage, manage billing information and quotes                                |   ✓   |   —   |    —   |
| Make someone an owner, or change or deactivate an owner                                       |   ✓   |   —   |    —   |
| Turn **Owners can open private items** on or off                                              |   ✓   |   —   |    —   |
| Archive the workspace                                                                         |   ✓   |   —   |    —   |

A workspace always has at least one owner. The last owner can't change their own role, be deactivated or leave until someone else is made an owner.

## Invite people

You need to be an owner or admin.

1. On the **Members** page, click **Invite people**.
2. Enter **Email addresses**, separated by commas or new lines. You can send up to 10 at a time.
3. Choose a **Role**: **Member** or **Admin**.
4. Click **Send 1 invitation**. The button counts the addresses, for example **Send 2 invitations**.

<figure><img src="https://3806122466-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk3DfNQKoMy1JXdaDLvpG%2Fuploads%2Fgit-blob-3e655461abcfe7837e27706388c488700a5b3a59%2Fdocs-workspaces-invite.gif?alt=media" alt="On the Members page click Invite people, type a teammate&#x27;s email address, leave the role on Member, click Send 1 invitation, and a Pending row appears in the list"><figcaption><p><strong>Invite people</strong> › email › <strong>Role</strong> › <strong>Send 1 invitation</strong>. The invitation waits as <strong>Pending</strong>.</p></figcaption></figure>

Nobody is invited as an owner. To make someone an owner, invite them and then change their role.

Each person gets an email from Biodock with a **Join \<workspace>** button. People who already have a Biodock account also get a **Workspace invitation** notification under the bell, and the invitation appears under **Invitations** in their account switcher. Someone who is already a member isn't invited again, and Biodock tells you so.

Invitations wait on the **Members** page as **Pending** until they're accepted. Open the **⋯** menu on an invitation to:

* **Resend invitation**: sends a new link and gives it another seven days. The old link stops working.
* **Revoke invitation**: withdraws it.

## Accept an invitation

1. Click **Join \<workspace>** in the email, or open the account switcher and click **Join** next to the workspace under **Invitations**.
2. The invitation page shows the workspace, who invited you and your role. Click **Join \<workspace>**, or **Decline**.

<figure><img src="https://3806122466-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk3DfNQKoMy1JXdaDLvpG%2Fuploads%2Fgit-blob-52f24c5ae63e59f8dbeb9b0b1e24d084438d6250%2Fdocs-workspaces-accept-invitation.gif?alt=media" alt="Signed in as the invited teammate, open the notification bell, open the workspace invitation, click Join and the workspace name, and land in the workspace"><figcaption><p>From the bell: the invitation › <strong>Join &#x3C;workspace></strong>. <strong>Invitations</strong> in the account switcher works the same way.</p></figcaption></figure>

* **The link works for seven days.** After that, ask the person who invited you for a new one.
* **Sign in with the invited email address.** If you're signed in with another account, the page says so and offers **Sign in with another account**.
* **No Biodock account yet?** Sign up with the invited email address. The link brings you back to the invitation.
* **Your email address must be verified** before you can see or accept an invitation. Until it is, the account switcher says *"1 invitation is waiting for you"* and asks you to verify your address. Open the link in the verification email, then click **I've verified**. Click **Resend email** if you can't find it.

Joining adds you to the workspace. Your personal account, its data and its credits stay separate and unchanged.

## Change someone's role

You need to be an owner or admin. On the **Members** page, pick a new role in the **Role** column.

* Admins can switch people between **Admin** and **Member**.
* Only owners can make someone an **Owner**, or change an owner's role.

## Remove someone (deactivate)

You need to be an owner or admin. Only owners can deactivate an owner.

1. On the **Members** page, open the **⋯** menu on the person's row and choose **Deactivate**.
2. Under **Who receives \<name>'s private items?**, choose a member. By default it's you.
3. Click **Deactivate**.

The person loses access to the workspace straight away, and their **Status** changes to **Deactivated**.

**What happens to their items:**

* Everything they made stays in the workspace.
* Their **private** items, the ones only people with access could see, are handed to the member you chose, who becomes their owner. Anyone else who had access keeps it.
* Items they had shared with everyone in the workspace stay as they are.
* Their personal account is not affected.

To let someone back in, open the **⋯** menu on their row and choose **Reactivate**. They come back with the role they had. Items that were handed over stay with the member who received them.

## Leave a workspace

1. Switch to the workspace and open **Members**.
2. Open the **⋯** menu on your own row and choose **Leave workspace**.
3. Choose who receives your private items. By default it's the longest-serving owner.
4. Click **Leave workspace**.

You lose access straight away, and Biodock takes you back to your personal account. Your status in the workspace becomes **Left**. Your personal account and everything in it stay as they are.

If you're the last owner, make someone else an owner first.

**Coming back after leaving** needs a new invitation. Someone who left can't be reactivated: Biodock says *"Someone who left has to be invited again rather than reactivated."*

## Working on a teammate's project

A project starts with the workspace's default access. If a teammate needs to label in a project that only some people can see, [share it with them](https://docs.biodock.ai/workspaces/workspaces/sharing-and-visibility.md#share-an-item) and give them **Can edit**. **Can view** lets them look but not label.


---

# 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.biodock.ai/workspaces/workspaces/members-and-roles.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.
