> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/collaboration-and-automation/notifications.md). # Notifications How Transform sends notifications and which settings control delivery. ### Overview Notifications surface changes that require attention. They reduce manual checking of views and lists. ### Key Concepts * **Trigger**: event that produces a notification * **Delivery channel**: in-app, email, or external destination (when configured) * **Signal**: notification types that represent action required ### How It’s Used Use notifications for high-signal events, such as mentions, assignments, and blockers. Disable low-signal events when noise reduces response quality. ### Benefits * Faster response to ownership changes * Fewer missed approvals and decisions * Cleaner accountability for due dates and blockers ### Setup Steps Most teams use notifications for: * assignments and reassignment * comments and `@mentions` * status changes * due date changes (or approaching due dates, if enabled) Delivery channels depend on Account configuration: * in-app notifications * email notifications * external destinations via Connectors (when enabled) ### Best Practices * Treat @mentions as action required. * Keep follow lists short to preserve signal. * Use Save Views for repeatable reviews instead of notification-driven navigation. ### Summary Start here: * [Notification Settings](/collaboration-and-automation/notification-settings.md) Related: * [Comments and Mentions](/collaboration-and-automation/comments-and-mentions.md) * [Following and Watching Items](/collaboration-and-automation/following-and-watching-items.md) * [Connectors](/administration/connectors.md) --- # 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://help.transform.ai/collaboration-and-automation/notifications.md?ask=&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.