> ## Documentation Index
> Fetch the complete documentation index at: https://docs.biomni.phylo.bio/llms.txt
> Use this file to discover all available pages before exploring further.

# Collaboration

> Share projects with members of your Team workspace

Team workspaces can share a project with selected active members or with the
whole workspace. Personal workspaces remain private.

Project sharing includes the project's tasks, files, results, notes, Drive
content, and other project-owned resources. Access is checked against current
workspace membership.

<Info>
  Chat access handoff is a beta feature and appears only in environments where it
  has been enabled.
</Info>

## Access levels

| Role       | What it allows                                                                                |
| ---------- | --------------------------------------------------------------------------------------------- |
| **Viewer** | Read tasks, files, notes, and results                                                         |
| **Editor** | Create tasks, continue chats handed to them, upload files, and change project content         |
| **Admin**  | Manage access and project settings, and delete the project when deletion requirements are met |

Every task has one person with chat access who can send messages and control it.
That person can hand off chat access to an active project Editor or Admin after
the current response finishes when the task belongs to a shared project. The
handoff button is in the task header next to Share; for unshared projects it is
disabled and explains that only sessions in shared projects can be transferred.
The previous participant immediately becomes read-only. Project Admins can
reassign chat access if the current participant is no longer available.
Session notes and creator attribution remain with the original task creator.

## Share a project

If you are a project Admin:

1. Open the project menu.
2. Select the sharing or member-management action.
3. Add a workspace member and choose Viewer, Editor, or Admin.
4. Save the changes.

Where enabled, you can also grant the entire workspace Viewer or Editor access.
Admin access must be assigned to an individual member.

## Working in a shared project

* Tasks display their creator and the participant with chat access.
* The current participant can use **Hand off chat access** to let one Editor or Admin
  continue the conversation. Multiple members cannot send messages at the same
  time.
* Project files and results inherit the project's access level.
* Viewers can open and download accessible files but cannot start compute or
  change project content.
* Editors can create their own tasks and add files, but cannot change sharing or
  project-wide instructions.
* Project context, custom instructions, and auto attached Skills are visible to
  members; only Admins can edit them.

<Warning>
  Removing a member's project access stops future access but does not delete work
  they created. Project deletion is blocked while other members still own project
  tasks/files or while compute and billing activity is unsettled.
</Warning>

For project structure and settings, see
[Projects & Drive](/features/projects-and-drive).