> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/project-management/workspaces/reference-workspaces/limitations.md). # 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.usemotion.com/help/project-management/workspaces/reference-workspaces/limitations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.