Workspaces & organizations

Collaboration in Consortium is built on organizations. One term needs disambiguating up front: in the CLI, your “active workspace” (consortium switch-org, consortium whoami) means your active organization. Inside the app, a workspace is a shared surface that lives within an organization. This page uses the app meaning.

Organizations

Every account has a personal organization; paid team plans add shared ones.

• Members & roles. Access is role-based: built-in and custom roles with a permission set and priority. Members can be active, suspended, or pending (invited).
• Keys. Each member holds the organization key wrapped to their own public key; invitations carry a wrapped key for the invitee.
• Limits (members, projects, spending cap, storage) come from the organization’s plan — see Pricing.

Note

Sharing inside an organization is enforced by server-side access control. Shared content is encrypted, and Consortium’s server distributes the wrapped keys — see Security & encryption for what that does and doesn’t guarantee.

Workspaces

A workspace is a shared layout of sessions and content — think of it as a team surface you arrange and return to.

• Visibility: shared (any member the roles allow) or private (explicit member list).
• Permissions: per-member view, edit, or manage; organization roles can also map to a workspace permission wholesale.
• Encryption: workspace content is encrypted under a workspace key; the layout structure and the workspace name are structural data the server can read.

Drive

Each organization (and each account) can have a Drive — encrypted file storage that sessions attach to.

• File and folder names and contents are encrypted per node; large files stream to blob storage as ciphertext.
• Per-member permissions: read, write, manage, each with the drive key wrapped to that member.
• Default quota is plan-based (500 MB on Free — see Free vs Pro); file version history is retained with plan-based depth.
• Session attachments land in Drive and are referenced from messages by ID.

Where agents fit

Sessions belong to a machine and a directory, and are visible to you (and, in team organizations, to members your roles allow). Workspaces and Drive are how a team shares the results — sessions, files, artifacts — not where the agent process runs.