> 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.md). # Reference: Workspaces ## Introduction A workspace in Motion is the top-level container for your account. It defines who you collaborate with, what projects and tasks are shared, and how calendars, docs, and settings apply across your team. Workspaces also control billing, roles, and permissions, making them the foundation for how Motion organizes both people and work. #### At a Glance * **Top-level container** → Everything in Motion — projects, tasks, docs, calendars — lives inside a workspace. * **Membership & roles** → Workspaces define who belongs to the team and what each person can do (Owner, Admin, Member, Guest). * **Permissions** → Roles govern who can create, edit, invite, or view across projects and docs. * **Calendars** → Workspace connections determine which external calendars feed into Motion. * **Cross-workspace separation** → Projects, tasks, and docs do not cross workspaces unless explicitly shared. * **Billing** → Subscription plans and usage apply at the workspace level. * **Limitations** → Workspaces cannot be merged, and guests have restricted access to shared resources. #### Conclusion Workspaces in Motion are the top-level containers that define how people, projects, and resources come together. They establish clear boundaries for collaboration, permissions, calendars, and billing. Each workspace is independent — with its own settings, members, and subscription plan — ensuring teams and organizations stay organized and secure. #### Key Takeaway A workspace is your team’s home base in Motion: it sets the rules for who can collaborate, what resources are shared, and how the account is billed. --- # 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.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.