When to create a teamspace
- A team owns multiple related projects.
- A product area needs a clear home.
- Demo, staging, and production work should be visually separated.
- You want recent projects and navigation to stay focused.
- You want imports, exports, and project discovery to stay organized.
Teamspace boundaries
Teamspaces are a navigation and ownership layer. Projects inside a teamspace can still have separate prompts, traces, deployment environments, datasets, and Behaviors. Workspace-level admins should still review provider credentials, API keys, members, billing, and security centrally.Suggested structures
| Structure | Use it when |
|---|---|
| By product team | Support, growth, product, and platform teams own separate AI workflows. |
| By customer segment | Enterprise, SMB, internal, or demo projects need separate operating context. |
| By lifecycle | Demo, staging, and production work should be visually separated. |
| By business unit | Several teams share a workspace but need clearer project ownership. |