> 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/~/revisions/q19CG9FaLRTUO6DpKHSc/navigating-motions-help-center.md).

# Navigating Motion's Help Center

Each Motion feature is separated into 4 different types of articles: 

### Type 1: Tutorials 

**Purpose**: These articles help you build feature familiarity.

**You can expect:** 

1. A 1-2 minute instruction showcasing how feature works.
2. Outlined goal, basic how-to guide, next steps to become a pro! 

### Type 2: How-to Guide

**Purpose**: Clear steps to complete a specific action.

**You can expect:** 

1. The instructions are task focused and shows you when to use and how to use the feature. 
2. A detailed step by step walkthrough on how the feature function.

The steps will be embedded within expandable blocks. Simply click on the drop down to unhide the steps. It looks like this: 

<details>

<summary>Steps: How to do an action in Motion</summary>

1. Step 1
2. Step 2
3. Step 3

{% hint style="info" %}
Some steps include a pro tip!
{% endhint %}

</details>

### Type 3: Reference

**Purpose**: Technical details of Motion's feature.

**You can expect:**&#x20;

1. Technical dictionary and rulebook
2. Limitations[^1]
3. [Definitions and terminology](#user-content-fn-2)[^2]
4. [Key properties](#user-content-fn-3)[^3]&#x20;
5. [Default behavior](#user-content-fn-4)[^4]
6. Error references
7. Troubleshooting

### Type 4: Concept&#x20;

**Purpose**: Outline insights, context, and rationale on why Motion built this feature.&#x20;

**You can expect:**&#x20;

1. Real-life examples and use cases show-casing the best example of how to use it.
2. The purpose / why we built this feature.

[^1]: &#x20;i.e. *A task can only be assigned to one user*

[^2]: Defines product specific vocabulary

[^3]: Cover system rules, data formats, integrations

[^4]: Describes the intended behavior


---

# 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:

```
GET https://www.usemotion.com/help/~/revisions/q19CG9FaLRTUO6DpKHSc/navigating-motions-help-center.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.