> 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/reference-data-hierarchy.md).

# Reference: Data Hierarchy

## Introduction

Data hierarchy in Motion defines how work is structured across different levels — from entire workspaces down to individual tasks. 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 tasks, with metadata and cross-cutting links layered on top.
* **Definitions** → Canonical explanations of each layer (workspace, folder, project, and task) 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
 │   │   └─ Docs
 │   └─ Docs
 └─ Docs
```

#### Conclusion

Data hierarchy in Motion provides a structured way to organize work across workspaces, folders, projects, tasks, and docs. 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.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.usemotion.com/help/knowledge-management/data-hierarchy/reference-data-hierarchy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.