# 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: 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/data-hierarchy.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.