Status: Available

Core rule

Organization membership does not automatically grant access to all labs or projects. Lab membership does not automatically grant access to all projects unless the lab’s default project access is open and your lab role is eligible (external collaborators are excluded from that inheritance).

Role hierarchy

Scope	Roles
Platform	`admin`, `user`
Organization	`owner`, `admin`, `member`
Lab	`owner` (PI), `admin`, `member`, `external_collaborator`, `viewer`
Project	`owner`, `admin`, `editor`, `viewer`

Permissions overview

Capability	Org owner/admin	Lab PI/admin	Lab member	External collaborator	Project editor	Project viewer
Manage org users / billing	Yes (role-dependent)	No	No	No	No	No
Manage lab members	If also lab admin/PI	Yes	No	No	No	No
See lab	If lab member	Yes	Yes	Yes (lab membership)	Only via project	Only via project
Inherit open-lab projects	If lab member (not external)	Yes	Yes	No — needs explicit project membership	N/A	N/A
Edit project content	Only if project role allows	Only if project role allows	Only if project role allows	Only if project role allows	Yes	No
Invite to project	Project admin/owner (typical)	May manage within lab policies	No	No	No	No

Inviting collaborators

Email invitations are for organizations and labs. An invitation can include project access. The recipient opens /invite/[token], then signs in or creates a password for that invitation.

The project Collaborators tab does not email a new account. It assigns admin, editor, or viewer to someone who already has an account.

After acceptance, check Collaborators or Members to confirm the role.

Personal projects

Personal projects are owned by a user. They are not automatically visible to an organization.

People chat on a project opens from the project header. It is a conversation with collaborators, not the assistant.