📖Reference: Data Hierarchy

Introduction

Data hierarchy in Motion defines how work is structured across different levels — from entire workspaces down to individual subtasks. Each layer has its own role, permissions, and scope, ensuring teams can organize, assign, and report on work consistently. This reference outlines the system rules for hierarchy, attributes, relationships, and lifecycle states.

At a glance

• Visual Model → A top-down map of how work is structured in Motion, from workspaces to subtasks, with metadata and cross-cutting links layered on top.

• Definitions → Canonical explanations of each layer (workspace, folder, project, task, subtask, and sheets) and their roles.

• Attributes → The core properties that define each item, including duration, dates, assignee, and ownership context.

• Relationships → How items connect through dependencies, references, cross-links, and parent–child nesting.

• Limitations → Known constraints on hierarchy, such as supported nesting levels, cross-workspace boundaries, and reporting implications.

Visual model

Workspace
 ├─ Folders
 │   ├─ Projects
 │   │   ├─ Tasks
 │   │   │   └─ Subtasks
 │   │   └─ Docs/Sheets
 │   └─ Docs/Sheets
 └─ Docs/Sheets

Conclusion

Data hierarchy in Motion provides a structured way to organize work across workspaces, folders, projects, tasks, subtasks, docs, and sheets. Each layer has defined rules for ownership, permissions, and relationships, while attributes and metadata overlay the hierarchy to support reporting and scheduling. Together, these rules create a consistent framework for organizing and connecting work inside Motion.