Notifications, mentions, and email digests

The bell next to Search in the workspace rail holds everything addressed to you: mentions (including assignment), replies, reactions, activity on records you follow, reminders, and Dench replies. Clicking a row opens the record — comment notifications scroll straight to the comment.

Kinds

Kind	Fires when
`mention`	someone `@`-mentions you, or a record is assigned to you
`comment_reply`	someone replies to your comment
`comment_reaction`	someone reacts to your comment (in-app only)
`entry_activity`	a record you follow gets a comment or field change
`dench_reply`	Dench answers a comment you left for it
`task_completed`	a task assigned to you is marked done
`date_reminder`	a date-field reminder you set fires
`automation` / `system`	automation output and workspace notices

task_assigned is a legacy kind for older assignment rows. New assignments are mention and show under the Mentions tab. The list filter mentions includes both.

Following records

You follow a record automatically when you create it, comment on it, are mentioned on it, or are assigned to it. The Follow toggle in a record’s Activity header (or dench crm watch … --off) unfollows; an explicit unfollow wins over later automatic follows. Followers get entry_activity notifications for other people’s comments and edits, coalesced to one per actor every ten minutes.

Email

Email is a digest by default — one message per window (12 hours) with a daily cap — so a busy record never floods an inbox. Direct mentions and replies still respect the same window. Adjust frequency, the daily cap, and per-kind delivery in Settings → Notifications.

CLI

dench notifications list [--filter inbox|unread|archived|all|mentions] [--limit N] --json
dench notifications count
dench notifications read <notificationId> [--unread]
dench notifications read-all
dench notifications archive <notificationId>
dench notifications prefs
dench notifications prefs --set emailEnabled=false --set entry_activity.email=false

Agent sessions (dench signin) read their owner’s inbox. An organization API key has no person behind it and is refused.

API

curl -sS "$DENCH_API_BASE/notifications?filter=mentions" -H "Authorization: Bearer $DENCH_API_KEY"
curl -sS "$DENCH_API_BASE/notifications/unread-count" -H "Authorization: Bearer $DENCH_API_KEY"
curl -sS -X PATCH "$DENCH_API_BASE/notifications/<id>" -H "Authorization: Bearer $DENCH_API_KEY" \
  -H "Content-Type: application/json" --data '{"read":true}'
curl -sS -X POST "$DENCH_API_BASE/notifications/read-all" -H "Authorization: Bearer $DENCH_API_KEY"
curl -sS -X PATCH "$DENCH_API_BASE/notifications/preferences" -H "Authorization: Bearer $DENCH_API_KEY" \
  -H "Content-Type: application/json" --data '{"perKind":{"entry_activity":{"email":false}}}'

Notification links are workspace-relative: /<workspace>?entry=<object>:<entryId>[&comment=<commentId>].

Start

Core

CLI

API

Notifications, mentions, and email digests

Kinds

Following records

Email

CLI

API

​Kinds

​Following records

​Email

​CLI

​API

Kinds

Following records

Email

CLI

API