> 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/definitions.md).

# Definitions

**Definitions**

<table><thead><tr><th width="130.8828125">Level</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Workspace</strong></td><td>The top-level boundary for an organization. Defines team membership, default permissions, and overall data visibility. All folders, projects, tasks, and docs exist inside a workspace.</td></tr><tr><td><strong>Folder</strong></td><td>A structural container used to organize work by theme, department, or taxonomy. Can contain projects, tasks, and docs.</td></tr><tr><td><strong>Project</strong></td><td>A goal-focused container that defines scope, schedule, and outcomes. Projects may include folders, tasks, subtasks, and docs.</td></tr><tr><td><strong>Task</strong></td><td>The atomic unit of work. A task has an assignee, due date, and status, and represents an actionable deliverable.</td></tr><tr><td><strong>Doc</strong></td><td>A flexible content space for notes, documentation, or AI-driven drafts. Docs can live at the workspace, folder, or project level.</td></tr></tbody></table>

**Cross-cutting layers**

* **Attributes** → Status, priority, labels, and custom fields apply across all levels.
* **Relationships** → Dependencies, references, and cross-project links connect items across the hierarchy.
* **Clarifications** → Docs can live anywhere in the hierarchy; Projects can also contain folders.


---

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