Skip to main content

​
Overview

Open Settings → Account → Notifications to review your personal notification history and preferences. The page has two tabs:
  • Inbox contains notifications addressed to your account.
  • Preferences contains personal channel, event, and Do Not Disturb settings.
Team delivery destinations are configured separately from the Notifications tab on each team.

​
Use the Inbox

​
Filter notifications

Select:
  • All notifications to show read and unread items
  • Unread only to focus on items that still require review
  • Action required to show critical or assigned work that needs explicit acknowledgement
The page loads notifications in batches. Select Load more when additional history is available.

​
Open the related record

When a notification references a case, alert, or task, select its entity link to open that record. Your normal role, team, organization, and TLP permissions still apply. Receiving a notification does not grant access to the referenced record.

​
Mark notifications as read

  • Select Mark read for an individual notification.
  • Select Mark all read to update all unread notifications in your inbox.
Reading an item does not acknowledge it. For an item marked Action required, select Acknowledge after accepting responsibility for the response.

​
Archive notification history

Archive an individual item from its action menu, or select Clear all to remove all items from the active inbox. Archiving does not destroy delivery or acknowledgement history. CaseBender retains lifecycle records according to the organization’s audit and retention policy. Archiving an inbox item does not delete the related case, alert, task, or activity.

​
Alert and case navigation badges

The Alerts and Cases badges show the exact number of records created since you last opened the corresponding list. Counts are stored per user and organization, survive refreshes and sign-in sessions, and include only records you are authorized to access. Opening the alert list advances only the alert cursor. Opening the case list advances only the case cursor.

​
Toast policy

CaseBender shows an interruptive toast only for a newly delivered Critical case notification (severity 4). Alert creation and non-critical case creation update durable badges and inbox state without producing toast noise. Replayed or historical notifications do not produce toast storms after reconnecting.

​
Configure notification channels

Open the Preferences tab and use Notification Channels to configure:
  • In-app notifications in the CaseBender notification center
  • Email notifications through your configured account email
Email delivery also depends on the CaseBender instance having a working outbound email configuration.
Channel preferences express how you want to receive notifications. Delivery can also depend on the event producer, system configuration, and destination availability.

​
Configure personal events

The Personal Notifications section includes controls for:
  • Items assigned to you
  • Mentions in comments
  • Replies to your comments
  • Updates to cases assigned to you
  • Task due reminders
Enable only the events that help you act on assigned work without creating unnecessary noise.

​
Configure Do Not Disturb

The Do Not Disturb section stores your preferred quiet-hour schedule. You can configure:
  • Whether Do Not Disturb is enabled
  • Start hour
  • End hour
  • Weekend inclusion
  • Whether critical alerts can override the schedule
Do Not Disturb must not be used as the sole control for paging, on-call coverage, or critical-incident escalation. Confirm critical delivery behavior through your organization’s approved alerting channels.

​
Personal versus team notifications

Personal preferences apply to notifications addressed to your user account. Team notification settings control shared destinations such as:
  • Slack workspaces and channels
  • Slack incoming webhooks
  • Microsoft Teams webhooks
  • Team email
  • Team-level case, alert, task, SLA, and escalation events
To configure a shared destination, go to Settings → Account → Teams, open a team, and select Notifications. You need team-management permission.

​
Access and data isolation

  • Every authenticated user can open their own notification page.
  • Notification queries and inbox actions are scoped to the signed-in user.
  • You cannot read, acknowledge, archive, or clear another user’s notifications.
  • Read-only roles can be restricted from preference-changing operations.
  • Access to linked records is evaluated separately.

​
Operational recommendations

​
Reduce noise deliberately

  • Keep assignment and mention notifications enabled for active responders.
  • Disable low-value events instead of ignoring the entire inbox.
  • Review preferences after changing teams or responsibilities.

​
Protect critical coverage

  • Allow critical overrides when required by policy.
  • Use team channels for shared operational coverage.
  • Test email and collaboration integrations after configuration changes.

​
Maintain the inbox

  • Mark items read after review.
  • Acknowledge actionable items separately from marking them read.
  • Follow the entity link before archiving an important notification.
  • Treat the inbox as a durable operational record governed by retention policy.

​
Troubleshooting

​
Email notifications are not arriving

Confirm that email notifications are enabled, verify your account email, and ask an administrator to check the outbound email integration.

​
A linked record is inaccessible

The notification does not bypass authorization. Request the appropriate organization, team, role, or TLP access.

​
My preference change is rejected

Your role can be read-only or your session might have expired. Sign in again or contact an administrator.

​
A team channel is not receiving events

Open the team’s Notifications tab and verify both the destination and the relevant event controls. Team configuration is independent of this personal page.

​
Related guides