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
@mentionsstatus 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:
Related:
Last updated