Notifications
Notifications is the in-app alert feed for system events—assignments, mention alerts, automation failures, approval requests, and module-specific updates. It is separate from the customer-facing Inbox (/inbox/inbox), which holds email and messaging threads. Think of Notifications as your operational radar: what changed in the workspace that needs a click-through action. The feed supports All, Unread, and Read tabs plus Mark all read for bulk cleanup after triage sessions.
Video
Who can do this
All signed-in workspace users. Some notification types appear only if you have permission on the related module.
Before you begin
- Notification preferences reviewed—know which categories email you vs. in-app only
- You understand difference between Notifications (system alerts) and Inbox (customer threads)
What you'll accomplish
- You can filter notifications by read state using tabs
- You can clear unread backlog with Mark all read when appropriate
- Deep links open the correct contact, task, deal, or settings page
- Unread badge on the header bell reflects accurate count
Step-by-step procedure
Open the notification feed
- Click the bell icon in the header, or navigate to
/notificationsif your workspace exposes the route directly. - Note the unread badge count on the bell—this syncs with the Unread tab.
Tab reference
| Tab | Shows |
|---|---|
| All | Every notification regardless of read state |
| Unread | Items you have not opened or marked read |
| Read | Previously viewed notifications for audit/reference |
- Start triage on Unread when the badge count is high.
- Click a notification row—the app navigates to the linked record (contact, task, approval, etc.).
- Complete the action on the destination page (approve leave, reply to mention, fix integration error).
- Return to Notifications; the item typically moves to Read automatically after click-through.
- When bulk-clearing low-priority items, switch to All, review nothing critical remains in Unread, then click Mark all read.
Triage priorities
Handle categories in this order during busy periods:
- Failures — Smart Flow errors, send failures, integration disconnects
- Assignments — inbox threads, tasks, deals routed to you
- Mentions — also listed in Mentions but may duplicate here
- Informational — reports ready, import complete, low-priority system messages
Reduce noise long-term
If the feed overwhelms daily work, open Notification preferences and disable email duplicates for categories you already monitor in-app. Admins can adjust Notification templates for customer-facing messages—distinct from this personal feed.
Notifications vs. Inbox
| Feed | Content |
|---|---|
| Notifications | System events about workspace objects |
| Inbox | Customer/partner message threads across Email, WhatsApp, Calls, SMS |
Verify your work
- Unread tab count matches bell badge before Mark all read
- Click-through lands on correct record with no permission error
- Mark all read zeroes badge; items appear under Read
- New events increment Unread after actions elsewhere in the app
Tips
Use Mark all read only after scanning Unread for failures and assignments—informational items can be bulk-cleared Friday afternoons. Pair with Mentions so @tags are not missed.
Troubleshooting
| Too many emails | Turn off email channel for noisy categories in preferences | | Missing expected alert | Category disabled in preferences or module not permitted for your role | | Deep link 404 | Source record deleted—mark read and ignore | | Badge stuck | Hard refresh; verify no service outage |