> 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/calendars-and-workspace-integration.md). # Calendars & Workspace Integration Workspaces control how calendars connect to Motion and how availability is shared across the team. Each member can link their own external calendars (Google, Outlook, iCloud), but calendar visibility and scheduling behavior are scoped to the workspace. **Behavior** * **Per-member connections** → Each workspace member connects their own external calendars. Motion never shares calendars across members automatically. * **Workspace visibility** → You can choose which of your connected calendars affect scheduling in the workspace (e.g., personal vs. work calendars). * **Scheduling impact** → Busy events from connected calendars block time in Motion, ensuring tasks and projects are scheduled only in open slots. * **Frequently Met With calendars** → Workspaces can also surface colleagues’ availability (read-only) for planning, without requiring full calendar access. * **Event sync** → Events sync bi-directionally, meaning changes in Motion reflect in your external calendar and vice versa. **Why it matters**\ Calendars determine availability across the workspace. By controlling which calendars connect and how they’re shared, you can keep scheduling accurate without overexposing personal or irrelevant events. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.usemotion.com/help/project-management/workspaces/reference-workspaces/calendars-and-workspace-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.