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

# Attributes

Attributes are metadata applied across items in Motion to track progress, priority, and reporting.

<table><thead><tr><th width="139.55078125">Attribute</th><th>Details</th></tr></thead><tbody><tr><td><strong>Status</strong></td><td>Indicates state of work (e.g., Active, Completed, Archived). Applies to tasks, and projects; used in reporting and scheduling.</td></tr><tr><td><strong>Priority</strong></td><td>Marks the relative importance of tasks. Often used to inform scheduling and focus views.</td></tr><tr><td><strong>Labels</strong></td><td>Flexible tags that can be applied to projects, tasks, or docs for grouping and filtering. Labels are not hierarchical and can overlap.</td></tr><tr><td><strong>Custom fields</strong></td><td>User-defined fields that add structured metadata (e.g., cost, region, team). Custom fields can be used in reporting and filters.</td></tr><tr><td><strong>Assignee</strong></td><td>Tasks require a single owner; projects may have an owner but support multiple collaborators.</td></tr><tr><td><strong>Dates</strong></td><td>Tasks and projects support scheduling with <strong>start date</strong> and <strong>deadline</strong> fields. These drive auto-scheduling and reporting.</td></tr><tr><td><strong>Duration</strong></td><td>Estimated time required to complete a task. Used by the scheduler to allocate blocks of work.</td></tr><tr><td><strong>Workspace</strong></td><td>Defines where the item lives. All items belong to a workspace, which sets default permissions and visibility.</td></tr><tr><td><strong>Projects</strong></td><td>Tasks can optionally be tagged to a project. If linked, the task inherits visibility, reporting, and scheduling from the project.</td></tr></tbody></table>


---

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