> 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/cross-workspace-separation.md).

# Cross-Workspace Separation

Workspaces in Motion are designed to be **independent containers**. Projects, tasks, docs, and calendars are scoped to the workspace they were created in, and do not carry over automatically to others.

**Behavior**

* **No automatic crossover** → A project created in one workspace cannot be seen or edited from another workspace.
* **User membership** → You can belong to multiple workspaces with the same Motion account, but your role and permissions are separate in each.
* **Calendars** → Calendar connections are also workspace-specific. A calendar linked in one workspace does not automatically apply to another.
* **Docs and tasks** → Items remain local to their workspace unless explicitly shared externally.
* **Notifications & inbox** → Each workspace has its own inbox and notification feed; activity does not combine across workspaces.

**Why it matters**\
Cross-workspace separation keeps data and permissions isolated. This is especially important if you manage different clients, teams, or organizations inside Motion — each workspace is its own secure boundary.


---

# 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/cross-workspace-separation.md?ask=<question>&goal=<endgoal>
```

`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.