> 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/time-management/inbox/reference-inbox.md).

# Reference: Inbox

## Introduction

Inbox is Motion’s centralized feed for product notifications. It aggregates task, project, notes, meeting insights, and team invite activity into one view with real-time updates, date filters, and quick actions that open the source item.

#### At a Glance

* **Supported types** → Inbox surfaces notifications from six categories: tasks, projects, notes, meeting insights, bookings and teams outputs.
* **Behavior & rules** → Notifications appear in reverse chronological order, update in real time, and support filters for unread and date groupings. Read/unread states sync across devices, and click-through opens the related item.
* **Limitations** → Inbox is optimized for immediate awareness, not long-term storage. Notifications auto-clean, cannot be pinned or searched, and only show activity from your current workspace.

#### Conclusion

Inbox centralizes all Motion notifications into a single, real-time feed. It supports six categories; tasks, projects, notes, meeting insights  with consistent rules for read/unread states, filtering, and cleanup. While optimized for high volumes, Inbox is lightweight by design, focusing on immediate awareness and quick click-throughs rather than long-term storage.

#### Key Takeaway

Inbox is the **live activity stream** in Motion: fast, filtered, and actionable, but not intended as an archive.


---

# 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/time-management/inbox/reference-inbox.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.