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

# Concept: Data Hierarchy

## Understanding Data Hierarchy in Motion

Every workspace needs structure. Without a clear hierarchy, projects get buried, tasks become hard to track, and permissions turn into a guessing game. Motion’s hierarchy solves this by giving your work a predictable shape — from the top-level workspace down to individual tasks.

A clear hierarchy matters because it:

* **Keeps work organized** → everyone knows where projects live and how they relate.
* **Controls visibility** → permissions flow by layer, so the right people see the right things.
* **Improves context** → metadata, relationships, and dependencies all make more sense when work lives in the right place.

Hierarchy isn’t about rules for their own sake. It’s about giving your team a consistent map so AI, employees, and teammates can navigate and act with confidence.

**At a Glance**

* **Mental model** → Motion’s hierarchy flows from Workspace → Folders → Projects → Tasks.
* **Core objects** → Each layer has a specific role: Folders group, Projects execute, Tasks track, break things down.
* **Relationships** → Containment (Folders → Projects → Tasks), Links (cross-references), and Dependencies (task-to-task).
* **Visibility & permissions** → Access is scoped by layer; workspace admins, folder/project owners, and task collaborators all see differently.
* **Metadata** → Some attributes apply globally (tags, owners), others at a local level (due dates, priority, status).
* **Lifecycle** → Work moves from creation → active execution → archive for reference.
* **Folder vs Project** → Folders are containers for themes or functions; Projects are for execution with timelines and deliverables.
* **Cross-cutting rules** → Naming, tagging, and search ability practices keep hierarchy usable at scale.

#### Conclusion

A well-defined hierarchy is what keeps Motion predictable and scalable. From top-level folders to the smallest tasks, structure ensures that work is easy to organize, permissions are clear, and AI has the context it needs to deliver accurate outputs. When hierarchy is applied consistently, teams spend less time searching or clarifying and more time executing.

#### Key Takeaway

**Data hierarchy is the backbone of Motion — it provides order, clarity, and context so people and AI can navigate, understand, and act on work with confidence.**


---

# 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/concept-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.