A workspace is an isolated environment: its own data, agents, integrations, and users. Use multiple workspaces for separate brands or regions with hard data boundaries; use teams within one workspace for everything else.
When to split workspaces
Hard boundaries only: separate legal entities, brands with independent CRMs, regions with data-residency requirements. Workspaces don't share Golden DB, suppressions, or reporting — that isolation is the point, and the cost.
When teams suffice
Same company, different squads → teams within one workspace: shared data, scoped views, unified suppression (critical — two workspaces can double-contact a prospect; two teams can't).
Creating and switching
Org admins create workspaces from the org console. Users with multi-workspace access switch via the workspace picker; role and scope are per-workspace.
Cross-workspace users
A user can hold different roles in different workspaces (Admin in sandbox, Member in production — a common and healthy pattern for change management).
