Skip to content
Governance5 min read

Multi-Tenancy, RBAC & Data Isolation

Company-scoped data partitioning, group/role access controls, server-only credential handling, and zero shared knowledge leakage.

Supply-chain companies manage competing shipper contracts under strict confidentiality agreements. An assistant working for NorthStar Logistics must never touch documents, threads, or settings belonging to Balkan Freight or Alecs CORP.

Strict company_id workspace partitioning

Every core domain entity—specialists, revisions, knowledge collections, documents, text chunks (pgvector rows), direct threads, group rooms, messages, tool runs, and team memberships—is keyed and filtered by company_id.

  • Cross-tenant API queries validate session authentication and active company membership server-side on every request.
  • Knowledge retrieval runs embeddings and full-text filters strictly inside the authenticated company's permitted collections—there is no shared global document index across tenants.

Team access groups & scoped capabilities

Under Company Access & Teams, administrators organize teammates into department teams (Dispatch Team, Warehouse Team, Customs) and inspect effective permissions cleanly:

  • Role hierarchy: member, company_admin, and platform_admin govern billing/settings/user invitation boundaries separately from operational document rights.
  • Granular resource grants: Access to individual specialists (Coca-Cola Assistant) and individual Knowledge Collections (retrieval_use vs view_content) can be tailored by team or individual without creating duplicate workspaces.

Server-side secrets & auditability

  • Encrypted provider keys and session secrets remain strictly server-side (apps/web/server), never serialized to browser bundles.
  • Run telemetry (run_events), tool approval logs (tool_invocations / approval statuses), and specialist_revisions preserve an auditable record of which rule version, source file, and human approval backed every decision.