About 5 min read
Workspaces and tenants
Per-customer runtimes, branded domains, SSO handoff, and why isolation is a product feature—not an afterthought.
One workspace, one boundary
A workspace is your unit of collaboration: members, agents, secrets, files, and operational history live together under explicit access rules.
In production deployments, that boundary often maps to an isolated tenant runtime so there is no accidental cross-customer data sharing at the application layer.
Domains and handoff
- Branded tenant domains improve trust and deep-linking for your end users.
- Login and signup flow through the control plane; successful auth hands you into the correct runtime with SSO semantics intact.
Lifecycle operations
Workspace deletion and data lifecycle are operator-grade concerns: schedules, confirmations, and purge paths exist so you are not stuck with silent orphans.
Exact knobs depend on your deployment contract—self-hosted, VPC, or Smart AI Team cloud—but the product model stays the same.
Related pages
- What is Smart AI Team? — Smart AI Team is the operational home for your AI workforce—workspaces, agents, tasks, and governed execution in one place.
- The AI operating layer for teams — Why a chat window is not enough, and how Smart AI Team maps intelligence onto real org structure and workflows.
- How it works — Control plane, tenant runtimes, sessions, skills, and channels—how the pieces fit without sacrificing isolation.
- Security, isolation, and governance — Tenant boundaries, secrets, metering, and operational patterns we use in production multi-tenant Smart AI Team.
- Documentation overview