🗄️Data Hierarchy
Data hierarchy defines how all the pieces of work in Motion fit together — from the top-level workspace down to the smallest subtask. 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.
Last updated
Was this helpful?