Notifications

Notifications keep staff informed about changes to items they own, watch, or approve.

Notification Types

ValueLabelDescription
mentionedMentionedWhen you are mentioned or tagged on an item.
assignedAssignedWhen you are assigned as staff owner or approver.
item_publishedItem PublishedWhen an agenda containing your items is published.
comment_addedComment AddedWhen a public comment is added to your item.
deadline_approachingDue date imminentWhen a workflow step on an item you own is approaching its due date or has passed it.
approval_requestedApproval RequestedWhen an item is submitted for your approval.
approver_approvedApprover ApprovedWhen an approver approves an item you watch, own, or approve.
approver_rejectedApprover BlockedWhen an approver blocks an item (advisory signal — flags concerns before publish).
approval_step_advancedReview RequestedWhen a routine step you're assigned to opens for approval.
approval_completedItem Fully ApprovedWhen every approver has approved an item (ready to publish).
sso_join_requestedJoin RequestsWhen someone signs in via single sign-on without an invite and needs to be admitted.

Who Gets Notified

Recipients are derived from their relationship to an item:

  1. Watchers — subscribed to updates on the item
  2. Staff owners — assigned as the item's staff owner
  3. Accountable staff — designated as accountable
  4. Approval chain — assigned to approval steps

You won't get duplicates — being both a watcher and the staff owner gets you one notification, not two.

Tip

The actor who triggers an event never receives the notification. If you publish an agenda containing your own items, you don't get notified about the publish.

Channels

  • In-app — appears in the notification inbox
  • Email — sent to the user's verified address

Preferences

Each user configures preferences per notification type, with independent toggles for in-app and email. Both default on.

Org admins can set org-wide defaults for users who haven't set their own. Order of precedence: your own preference, then the org default, then the event's audience rule.

Background Delivery

Notifications are sent in the background, usually within a few seconds. Failed deliveries (for example, a temporary email-provider error) are retried automatically.

Related

Notifications - Livy Docs — Livy