Limitations
Workspaces provide a secure and structured boundary for teams, but there are some constraints to be aware of:
No merging β Two workspaces cannot be merged; projects, tasks, and docs must be recreated or manually migrated if consolidation is needed.
Data isolation β Content (projects, tasks, docs) cannot be shared natively across workspaces. You must invite a user into the target workspace or export/import content.
Single billing plan β Each workspace operates under one subscription tier; you cannot mix different tiers within the same workspace.
Role restrictions β Guests have limited functionality and cannot create projects, manage calendars, or access advanced features.
Calendar scope β Calendars are connected at the member level and scoped to the workspace; the same calendar must be reconnected separately if you use multiple workspaces.
No global search β Search is workspace-specific; you cannot search across multiple workspaces at once.
Owner dependency β Each workspace must have at least one Owner; ownership cannot be removed without reassigning.
Key Takeaway Workspaces are intentionally siloed. They create a clear boundary for collaboration, billing, and permissions β but this also means data and settings do not transfer across them.
Last updated
Was this helpful?