> 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/knowledge-management/docs/reference-docs.md).

# Reference: Docs

## Introduction

Motion Docs is the document system inside Motion that supports writing, editing, collaboration, and publishing directly within your workspace. This reference outlines the system rules that define how Docs behave — from structure and formatting to access, versioning, and reliability. It provides a factual overview of what Motion Docs supports, what limits apply, and how documents connect with the rest of Motion.

## At a Glance

#### 1. Structure & Model

* **Core Model** → How Docs are created, stored, and linked.
* **Organization and Hierarchy** → Inheritance and structure within workspaces, folders, and projects.
* **Creation and Placement** → Rules for where new Docs appear and how context is inherited.

#### 2. Content & Editing

* **Editing and Blocks** → Block-based editing rules for text, lists, and media.
* **Formatting and Presentation** → Supported text styles, lists, and block-level formatting.
* **Turn Notes Into Scheduled Work** → Converting content into tasks and projects.

#### 3. Collaboration & Access

* **Collaboration and Access** → Permissions and visibility rules for individuals and teams.
* **Publishing and Versioning** → Updates, history, and restoring versions.

#### 4. Discovery & Boundaries

* **Navigation and Discovery** → Search, filters, and surfacing Docs in context.
* **Limits, Reliability, and Edge Cases** → Boundaries and constraints of the Docs system.

#### What You’ll Learn

By the end of this reference, you’ll understand the system rules that govern Motion Docs — how they are created, structured, edited, shared, and versioned. You’ll also know the limits and behaviors to expect when working with Docs, so you can rely on them for accurate collaboration and task management.

<br>


---

# 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/knowledge-management/docs/reference-docs.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.