About 6 min read
Security, isolation, and governance
Tenant boundaries, secrets, metering, and operational patterns we use in production multi-tenant Smart AI Team.
Tenant isolation as a default
We design for strong separation between customers: separate services, environment boundaries, and metering per tenant where the platform model requires it.
The control plane orchestrates; it is not a shortcut into another customer's runtime.
Secrets and connectors
- Connector credentials and sensitive values belong in governed stores—not pasted into prompts.
- Agent capabilities should be allowlisted and observable so security teams can reason about blast radius.
Operational posture
Scale-to-zero friendly control plane components reduce cost and attack surface when idle, without blocking provisioning queues from completing reliably.
Health surfaces in the workspace help operators see agent status, gateway connectivity, and integration drift before users do.
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.
- Workspaces and tenants — Per-customer runtimes, branded domains, SSO handoff, and why isolation is a product feature—not an afterthought.
- Documentation overview