# Structure & Model **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. *** ## Core Model The Core Model defines the structure of Motion Docs — how documents are stored, represented, and linked within a workspace.

Feature	Details
Canvas vs. blocks	Each Doc is a canvas made up of individual blocks. Blocks are the basic editing unit (text, list, task, or media). The canvas provides structure for arranging and nesting blocks.
Block types & hierarchy	Blocks follow a parent–child hierarchy. A parent block controls the behavior of its children: moving, collapsing, or deleting the parent also affects its child blocks. Lists and checklists are the clearest example — a main bullet is the parent, and its indented sub-bullets are children. Headings, by contrast, provide visual grouping but do not impose structural hierarchy on the blocks that follow.
Sub-Docs & parent-child linking	A Doc can contain Sub-Docs that are linked to their parent. By default, Sub-Docs inherit the parent Doc’s location and sharing settings, making them easy to organize and collaborate on. This link is not permanent — a Sub-Doc can be disconnected from its parent and moved or shared independently if needed.
Icon doc	Each Doc displays a color and icon for quick identification. Colors and icons are applied at the Doc level and remain visible in search, navigation, and references.
Workspace-level storage & ownership	All Docs are stored at the workspace level. Ownership and access follow workspace permissions. A private doc should be in your private workspace.

## Organization and Hierarchy Organization and hierarchy define how Motion Docs are structured and arranged within a workspace.

Feature	Details
Workspace, folder, project, doc nesting	Docs live at the workspace level and can be placed inside folders or projects. Nesting rules follow a parent → child relationship (workspace → folder/project → doc → sub-docs).
Linking between docs and blocks	Docs and individual blocks can be linked directly. Copy link provides a persistent reference to the selected Doc or block.
Move, rename, and drag-drop	Docs and folders can be renamed at any time. Items can be moved or reordered using drag-and-drop within the workspace hierarchy.
Favorites	Docs or folders can be marked as favorites. Favorites can be added or removed at any time, and appear in the sidebar. Sorting follows the order items are favorited; manual re-ordering is not supported.

## Creation and Placement Creation and placement define where new Docs appear, how they inherit context, and how permissions apply after creation.

Feature	Details
Left sidebar “New” flow	Creating a new Doc from the New (+) button in the sidebar places it in the currently selected workspace by default.
Permission inheritance	New Docs inherit the sharing and permissions of their parent folder or project. Permissions can be adjusted manually after creation.
Cross-workspace sharing	Docs are created in a single workspace. After creation, they can be shared to additional workspaces via the Share dialog.
Mobile parity	Creating Docs on mobile follows the same location and inheritance rules as desktop. Some advanced placement actions (e.g., drag-drop reordering) may be limited on mobile.

--- # Agent Instructions: 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: ``` GET https://www.usemotion.com/help/knowledge-management/docs/reference-docs/structure-and-model.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.