- Documentation
- How it works
About 6 min read
How it works
Control plane, tenant runtimes, sessions, skills, and channels—how the pieces fit without sacrificing isolation.
On this page
Two planes, one experience
The control plane handles authentication, onboarding, provisioning, billing alignment, and launching you into the right workspace.
Each workspace runs on a dedicated tenant runtime: agents, APIs, office surfaces, and metering execute there so customer boundaries stay crisp.
Provisioning and launch
- Workspaces are provisioned asynchronously so sign-up stays fast even when infrastructure work continues in the background.
- When tenant domain mapping is enabled, customer-facing URLs prefer branded subdomains over raw infrastructure endpoints.
- SSO handoff uses a time-bounded shared secret so control plane and runtime trust each other without weakening isolation.
Inside the runtime
Agents consume a unified prompting and tool stack across chat, pulse, cron, meetings, and external channels where enabled.
Skills and workspace templates let you encode repeatable expertise so new agents start useful—not blank.
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.
- Workspaces and tenants — Per-customer runtimes, branded domains, SSO handoff, and why isolation is a product feature—not an afterthought.
- Security, isolation, and governance — Tenant boundaries, secrets, metering, and operational patterns we use in production multi-tenant Smart AI Team.
- Documentation overview