> 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/getting-started/navigation-basics/navigating-motion-features.md).

# Navigating Motion Features

## Introduction

Motion brings together all your work: tasks, projects, meetings, notes, and AI features in one place. To get the most out of Motion, it helps to know where everything lives and how to move between sections quickly.

This guide walks you through how to navigate the core areas of Motion, from AI Chat to Docs, so you can find what you need and take action without friction.

#### At a Glance

In this guide, you’ll learn how to navigate:

{% tabs %}
{% tab title="AI Features" %}

#### **AI Features**

* **AI Chat:** Start conversations with Motion AI, ask questions, and act on recommendations directly.
* **AI Meeting Notes** – review transcripts, summaries, and action items.
* **Inbox:** Collect all tasks, messages, and notifications in one central hub for quick triage.
* **AI Agenda:** Treat your agenda like a doc — reorder, edit, and add tasks inline while tracking today’s work.
  {% endtab %}

{% tab title="Project Management Features" %}

#### Project Management Features

* **Workspaces** – switch between personal and team spaces.
* **Projects & Tasks** – organize, assign, and manage your work.
* **Views & Dashboards** – visualize progress and workload.
* **Docs** – draft, edit, and share documents.
  {% endtab %}
  {% endtabs %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.usemotion.com/help/getting-started/navigation-basics/navigating-motion-features.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
