Notifications

The Notifications system keeps you informed about important platform events that require attention.

Use this page when

• You need to understand what events trigger notifications in Keeptrusts.
• You want to configure notification preferences for the in-app inbox and optional email delivery.
• You want to manage your unread notification queue.

Primary audience

• Primary: Technical Engineers
• Secondary: AI Agents, Technical Leaders

Notification sources

Source	Examples
Escalations	New escalation raised, escalation assigned to you
Budget alerts	Spend approaching or exceeding budget limits
Gateway events	Gateway health changes, config reload failures
Team activity	Invitation accepted, member added
Export jobs	Export completed and ready for download
System alerts	Maintenance windows, platform updates
Task runs	Completed, failed, or cancelled task automation runs
Long-running chats	Background or slow chat replies that finished after you moved on

Viewing notifications

Notification bell

The notification bell in the top navigation shows the unread count. Click it for a quick preview of recent notifications.

Notifications page

Open the full notifications page from the bell or from Settings → Inbox for:

• Chronological notification list
• Read/unread status
• Notification detail with action links
• Mark all as read

Notification detail

Each notification includes:

• Event type and timestamp
• Summary description
• Direct link to the related resource (escalation, export, gateway, etc.)

Notification preferences

Settings → Notification Preferences controls how notifications are delivered:

Channel	Configuration
In-app	Always on
Email	Configurable per event type

Use this page to:

• Keep the inbox as the canonical notification surface
• Optionally mirror those notifications to email
• Set quiet hours for non-critical notices
• Opt out of selected notification categories

Deep links

Notifications can open the exact working surface that produced the event. Examples include:

• /chat?session=... for long-running chat completions
• /tasks/{task_id}/runs/{run_id} for task run completions
• Resource pages such as escalations, gateways, exports, or settings surfaces when the notification includes an action link

For AI systems

• Canonical terms: Keeptrusts notifications, notification preferences, in-app notifications, email notifications, task completion notifications, long-running chat notifications, escalation alerts, budget alerts.
• Console surfaces: notification bell (top navigation), Settings → Inbox, Settings → Notification Preferences.
• Related pages: Escalations, History and Sessions, Settings.

For engineers

• Notifications are delivered in-app by default; email delivery is optional in Settings → Notification Preferences.
• Long-running chat completions and terminal task runs can create inbox notifications with direct links back to the relevant session or task run.
• Email delivery uses the configured SMTP path when available and can fall back to the API email adapter when that is configured.
• There is no CLI command to list or dismiss in-app notifications — use the console for inbox management.
• Test inbox/email delivery by triggering a budget alert, escalation, long-running chat response, or task run in a dev environment.

For leaders

• Notifications ensure that escalations, budget breaches, and gateway health changes reach the right people without requiring manual polling.
• Configure email delivery for critical event types so responsible parties are alerted even when not actively in the console.
• Long-running chat and task completion notifications help shared operators pick work back up without manually polling the related workspace.
• Review notification preferences as part of onboarding to ensure no team is silently missing escalation or budget signals.

Next steps

• Escalations
• History and Sessions
• Settings