Skip to main content
Workspaces are the primary tenancy boundary in Uno. Operators authenticate through Supabase, join workspaces via membership, and attach repositories that drive seed snapshots and sandbox work.

Key ideas

  • Identity lives in Supabase Auth and profile tables.
  • Membership controls who can operate within a workspace.
  • Repositories attach to workspaces and feed seed snapshot generation.
  • Sandboxes are provisioned from active seed snapshots for sessions and builds.

Personal workspace on sign-up

Every confirmed product user receives one personal workspace automatically. The workspace name defaults to your display name when you create an account. You become the owner member immediately after email confirmation. See Create an account for the full provisioning flow.

Coming next

Future docs will cover workspace settings, roles, repository attachment, and wiki parity.