A dedicated full-page workspace for triaging, archiving, snoozing, filtering, and searching every notification you have received.
The inbox is the full-page view of every notification — beyond what fits in the bell dropdown.
Open /notifications from the Notifications entry in the left sidebar, from the View all notifications link at the bottom of the bell dropdown, or by pressingG then I from anywhere in the app. The inbox shows every notification you have received, grouped by day, with infinite scroll to load older history as you reach the bottom.
Switch between four views of your notifications.
All filters sync to the URL so you can bookmark or share a view.
| Field | Description |
|---|---|
| Reason | The primary quick-filter, leading the filter row. Single-select by why a notification reached you: Any reason, Assigned to you, You were mentioned, You are watching, You own this, or Admin copy. It is often the fastest way to show just the things aimed directly at you, or just the ambient updates. |
| Search | Free-text search over the notification title and message. Results update as you type. Press / from anywhere on the page to focus the search input. |
| Type | Multi-select by notification type: @Mention, Task Assigned, Deal Stage Changed, Approval Request, Ticket Reply, Goal Achieved, Campaign Completed, and every other supported type. Types are grouped by the same categories shown in the settings page. |
| Priority | Multi-select by priority: low, medium, high, or urgent. |
| Entity | Filter by the related entity type: Company, Person, Deal, Task, Ticket, Activity, Project, Invoice, Quote, Campaign, Meeting, Goal, Agent Run, AI Chat Run, or Workflow. |
| Needs action | A single toggle that narrows the list to only the notifications that need an action from you (the same action-required types that can be sent to My Work). Turn it on to focus on what you have to act on, off to see everything again. |
Rows encode state through weight, a single accent, and text, never color alone.
Every notification row has quick-action buttons that appear on hover or focus.
The inbox is for things that happened — your to-do list lives in My Work.
A dismissible note at the top of the inbox states the rule plainly: "These are things that happened. Anything you need to do lives in My work." The two surfaces have clear, non-overlapping jobs:
Selecting a row on desktop shows the full notification on the right.
The detail pane shows the full notification title, the complete message (no truncation), the notification timestamp, who sent it (for mentions and nudges), the priority, and a Related card naming the linked entity type. Action buttons at the bottom repeat the per-row actions: Open, Mark read / Mark unread, Snooze, and Archive.
When a notification is about something you can decide on the spot, the detail pane offers the action inline. An approval request, for example, shows Approve and Deny buttons right in the detail view, so you can clear it without opening another page. Acting on it there does the same thing as acting on it in its own surface, and it clears the matching item from My Work at the same time. See My Work vs Notifications for the full list of inline actions.
Select multiple notifications and act on them together.
Click the checkbox on each row to build a selection, or use the Select all visibletri-state checkbox in the inbox header to select every loaded row at once. The header checkbox shows an indeterminate (mixed) state when some — but not all — visible rows are selected, and toggles to clear or fully select on click. A bulk-action toolbar appears at the bottom of the list pane showing N selected and the available actions:
Clear the entire unread badge with one click.
When there are unread notifications, a Mark all as read button appears in the inbox header next to the unread count badge. It is rendered as a primary-tinted pill so it reads as an actionable affordance — not a passive link. Clicking it marks every unread notification in your account as read (not just the ones currently loaded), updates the bell badge to zero, and surfaces a confirmation toast like "30 notifications marked as read". The reported count comes from the server and reflects the real number of rows that flipped from unread to read — re-clicking after everything is already read is a safe no-op.
Navigate and act on notifications without touching the mouse.
Rows group into Today, Yesterday, This week, and Older buckets, with sticky headers as you scroll.
Notifications are grouped by day as you scroll, with sticky section headers so you always know which bucket you are reading. The list uses infinite scroll: 25 notifications load initially, and reaching the bottom automatically loads the next batch. A Load more button also appears if auto-loading is blocked by your browser. You can change how the list is grouped (by date, type, priority, or a single flat list) in your inbox view preferences.
What you see when there is nothing to show.
Each tab shows a tab-specific message; the icon distinguishes "you're caught up" (a green checkmarkicon) from "your filters returned nothing" (a muted bell-with-slash icon).
When to use each surface.
The bell dropdown in the top bar shows your 30 most recent notifications across four tabs (All, Unread, Mentions, Assigned). Each row exposes up to three quick actions on the right: an Open button (a chevron) when the notification links somewhere, a Snooze button (a clock icon that opens a small menu with 1 hour, 4 hours, or Tomorrow) where snoozing makes sense, and a first-class Dismiss button (the X icon) that always appears and clears the notification from the bell in one click (it moves to the Archived tab). Opening the bell automatically marks every loaded unread item as read, the same behavior used by Facebook, LinkedIn, and Slack, so you no longer need to navigate to the inbox just to clear the badge for items you have already seen. New notifications that arrive after the bell is open are not auto-marked. The full inbox at /notifications adds search, filter chips, bulk operations, keyboard navigation, the detail pane, and infinite history. Use it when you need to triage a larger backlog or find something specific.
Read, archive, snooze, and delete actions propagate to every open tab in real time.
If you have the CRM open in multiple browser tabs, marking a notification read in one tab clears it from the bell, the sidebar badge, and the inbox in every other tab — usually within ~10 ms. The same applies to archive, snooze, delete, and bulk operations. There is no extra polling cost: tabs communicate directly through the browser's same-origin BroadcastChannel. Account-switching is protected — broadcasts from a different signed-in user or organization are ignored, and the unread count always reflects the server's authoritative value rather than a guess.
What happens when an action fails.
Mark-read, archive, snooze, and delete all use optimistic updates: the row visually flips immediately and the network request runs in the background. If the request fails (network drop, server error, or a race with another tab), the change rolls back and a small toast surfaces in the corner — "Couldn't mark this notification as read", "Couldn't archive this notification", etc. The toast is your cue to retry; the row returns to its previous state in the meantime.