> 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/notification-types-behaviors-and-limitations.md).

# Notification Types, Behaviors & Limitations

## **Supported Notification Types (6 categories)**

<table><thead><tr><th width="167.4765625">Category</th><th>Examples shown in inbox</th></tr></thead><tbody><tr><td><strong>Tasks</strong></td><td>Assigned to you; mentioned in a comment; status updated; bulk operation applied; comment reaction.</td></tr><tr><td><strong>Projects</strong></td><td>Project status updated; mentioned in a project comment; project stage entered; stage status updated.</td></tr><tr><td><strong>Notes (Docs)</strong></td><td>Mentioned in a document; mentioned in a document comment.</td></tr><tr><td><strong>Meeting Insights</strong></td><td>Meeting completed (insight available).</td></tr></tbody></table>

## Behavior & Rules

Inbox follows consistent rules for how notifications appear, update, and clear:

<table><thead><tr><th width="205.73828125">Rule</th><th>Details</th></tr></thead><tbody><tr><td><strong>Ordering</strong></td><td>Notifications appear in reverse chronological order (newest at the top).</td></tr><tr><td><strong>Read/Unread state</strong></td><td>Unread items are highlighted. Clicking an item marks it as read. States sync across devices.</td></tr><tr><td><strong>Filters</strong></td><td>Inbox supports filtering by <strong>Unread only</strong> or by date groups (<strong>Today</strong>, <strong>Yesterday</strong>, and earlier).</td></tr><tr><td><strong>Bulk actions</strong></td><td>Use <strong>Mark all as read</strong> to clear the feed in one step.</td></tr><tr><td><strong>Real-time updates</strong></td><td>New notifications appear instantly; no refresh required.</td></tr><tr><td><strong>Click-through behavior</strong></td><td>Selecting an item opens the related task, project, doc, or booking in its source location.</td></tr><tr><td><strong>Permissions</strong></td><td>Inbox only shows notifications for items you have access to within your workspace.</td></tr></tbody></table>

## Limitations

Inbox has defined boundaries for what it does and does not support:

<table><thead><tr><th width="191.6484375">Category</th><th>Limitations</th></tr></thead><tbody><tr><td><strong>Retention</strong></td><td>Notifications are stored indefinitely until you delete them.</td></tr><tr><td><strong>Pinning</strong></td><td>Notifications cannot be pinned or saved for later. Once cleared, they are removed from the feed.</td></tr><tr><td><strong>Customization</strong></td><td>Notification categories cannot be turned on/off individually; all supported types appear if relevant to you. Update your notification setting to hide the notifications you don't want to see.</td></tr><tr><td><strong>Cross-workspace scope</strong></td><td>Notifications are workspace-specific. You will not see updates from other workspaces in the same feed.</td></tr><tr><td><strong>Granularity</strong></td><td>Inbox surfaces discrete notifications only; it does not display bulk reporting or analytics.</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/time-management/inbox/reference-inbox/notification-types-behaviors-and-limitations.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.