Workspace/Workspace

Workspace

Projects, people, seats, and settings — how the room is shaped.

Workspace

Workspace is the room container: projects, people, seats / roles, and settings (including standing instructions). Operators run the collab OS here; viewers follow and consume with a thinner shell.

Where in the product

Where in the product

People and roles under membership surfaces; projects from the Projects rail; plan and seat inventory under billing for admins.

Settings / PeopleProjectsBilling · seats (admin)

Roles & seats (Spine+)

Every member has one role:

RoleSeat classJob
ViewerCollab seatFollow Work, Artifacts, Calendar, Projects — no AI send, no work-graph mutations
EditorAI seatFull operator: chat, work, agents, artifacts
AdminAI seatEditor powers + people, billing, workspace settings

Owner is always an admin for the room (not a fourth role). Included capacity (AI pool) hard-stops burn when exhausted — it does not demote roles. Seat inventory shrink can demote excess AI operators to viewer, or hard-lock members who no longer fit.

Viewer shell

Collab seats see rail Work · Artifacts · Calendar · Projects only — no Chat rail icon, no Agents/Routines extras as destinations. Home may open a chat shell with composer locked.

Projects (Spine+)

Projects group tasks and artifacts. Unfiled work and images can live at workspace scope; bind to a project when you want a clearer boundary.

Settings tour (Spine+)

Use workspace settings for name, branding, and standing instructions (room policy — not skills). Admins manage invites, roles, and billing; editors operate day-to-day work without owning room danger actions reserved for the owner.

Key distinctions

  • Plan price (Free / Pro / Max) is not a seat SKU.
  • AI seat ≠ collab seat.
  • Viewers are first-class stakeholders, not “guests.”