> 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/data-hierarchy.md). # Data Hierarchy Data hierarchy defines how all the pieces of work in Motion fit together — from the top-level workspace down to individual tasks. It determines how items are organized, how they inherit attributes, and how they interact through dependencies, permissions, and reporting. Understanding hierarchy is essential for both **day-to-day use** (creating, assigning, and tracking tasks) and **long-term planning** (structuring projects, folders, and workspaces so they scale with your team). This section contains two types of articles: * **Reference** → Covers the technical “what” of hierarchy, including **definitions, attributes, relationships, and limitations**. * **Concept** → Explains the “why” behind the model, introducing the **mental framework, metadata layers, lifecycle rules, folder vs. project choices, and cross-cutting patterns** that guide best practices. Together, these guides provide both the **precise details** and the **big-picture understanding** you’ll need to work confidently with Motion’s hierarchy. --- # 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/knowledge-management/data-hierarchy.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.