Workspace and organizational structure

Status: Available

Hierarchy

Organization
  └── Lab (research group; PI = lab owner)
        └── Project (Hub workspace)
              ├── Samples, datasets, files
              ├── Analyses and artifacts
              ├── Labbook, memory, tasks
              └── Reports and logs

Organization

• Route: /organizations (and org settings, billing, and organization memory).
• Academia Researcher can check out in the app. Other plans are not self-serve.
• Roles: owner, admin, member.
• Org membership does not automatically grant lab or project access.

Lab

• Route: /labs, /labs/[labId], members, settings, labbook, memory.
• Roles: owner (shown as PI in the UI), admin, member, external_collaborator, viewer.
• Labs can configure default project access (for example open inheritance for non-external members). External collaborators do not inherit open-lab project access; they need explicit project membership.

Project

• Canonical routes: /hub and /hub/[projectId]/....
• Legacy-style /projects/[projectId]/... aliases exist for many pages; prefer Hub URLs.
• Roles: owner, admin, editor, viewer.
• Projects may be personal or associated with a lab.

Personal vs organizational work

• Personal projects are owned by a user and are not interchangeable with org-wide visibility.
• Lab-linked projects can inherit access for eligible lab members when the lab’s default project access is open.
• Organizational memory and lab memory are separate surfaces from project memory.

Sharing content

Content is shared by granting membership at the correct level:

1. Invite to organization (does not open all labs).
2. Add to lab (does not open all projects unless inheritance applies).
3. Add to project (or rely on open-lab inheritance for eligible roles).

See Collaboration and permissions for a full matrix.