Workspaces and Organizations

SupaCloud uses one term for one meaning across the database, API, and UI. The word team used to be overloaded; it is now reserved for the agent domain only.

The hierarchy

• Organization — the top tenant. It owns billing/seats, SSO, and invitations. Every user belongs to exactly one organization. A personal organization is auto-provisioned on signup.
• Workspace — the resource container under an organization. Projects, tasks, runs, workflows, schedules, secrets, and connectors all live in a workspace. Membership is by user.
• Project / Task / Run / Workflow / Connector — resources inside a workspace.

The server derives the active organization from the active workspace — there is no organization switcher.

Why not “team”?

Team and Teammates are reserved for the agent domain — a multi-agent group spawned for one task. The tenant is always a Workspace; the top tenant is always an Organization.

Ubiquitous-language rule

Never use “team” for the tenant. This rule is enforced in CI by an architecture test (no new team_id tenant column) and a frontend i18n-lint rule (no new user-facing “Team” string outside the agent and delivery-board namespaces).

Entitlements

What a workspace can do is resolved by first-non-null priority: user override → seat type → workspace override → organization plan → default, composed under the deployment edition. A seat can never grant an edition-gated feature.

This vocabulary is the subject of ADR 0040 and the organization tenancy model is ADR 0035.