Tutorial: Setting Up Notification Delivery

This tutorial walks you through the current Keeptrusts notification model: an always-on in-app inbox with optional email delivery for the same events.

Use this page when

• You want to understand how Keeptrusts delivers notifications today.
• You need to enable or disable email delivery for your own notifications or your team defaults.
• You want to configure quiet hours or mute selected notification categories.
• You want to verify that inbox and email notifications deep-link back to the right console surface.

Primary audience

• Primary: Platform engineers and on-call operators setting up real-time alerting for AI governance events
• Secondary: Team leads configuring team-specific notification routing; security analysts monitoring for policy violation alerts

Prerequisites

• A Keeptrusts account with permission to open Settings → Notification Preferences
• A valid email address if you want Keeptrusts to mirror inbox notifications to email

How notification delivery works

Keeptrusts uses two delivery surfaces:

• In-app inbox: always on for the signed-in user or the active team-default context
• Email: optional; mirrors matching inbox notifications to an email recipient

This means you do not need to choose between inbox and email. The inbox remains the canonical record, and email is an add-on for people who are away from the console.

Step 1: Navigate to Notifications

1. Log in to the Keeptrusts console.
2. Open the notification bell to preview recent unread items.
3. Open Settings → Inbox to review the full notification queue.
4. Open Settings → Notification Preferences to manage delivery behavior.

From there you can:

• Read or clear notifications
• Follow action links back to chats, task runs, escalations, and gateway surfaces
• Turn email delivery on or off
• Configure quiet hours
• Mute selected categories

Step 2: Review the always-on inbox

The inbox is the canonical notification surface and cannot be disabled.

1. Open Settings → Inbox.
2. Confirm the page lists unread and read notifications in chronological order.
3. Open a notification detail panel and verify the action link points back to the relevant surface.
4. Use Mark all as read only after you have reviewed the queue.

Examples of inbox deep links:

• Long-running chat completion → /chat?session=<history-session-id>
• Task completion → /tasks/<task-id>/runs/<run-id>
• Escalation or gateway events → the related detail or workbench page

Step 3: Enable optional email delivery

Email is the only supported external delivery channel for notification preferences.

1. Click your profile avatar in the top-right corner.
2. Select Notification Preferences.
3. In Delivery Channels, confirm In-app inbox shows as Always on.
4. Turn on Send notifications by email if you want matching alerts outside the console.
5. Optionally set Override email recipient if the default signed-in email is not the right target.
6. Click Save preferences.

Email notifications include a short summary plus a direct link back to the related resource in the console.

Step 4: Configure quiet hours

Quiet hours suppress non-critical notifications during the hours you choose.

1. In Notification Preferences, open the Quiet Hours section.
2. Turn on Enable quiet hours.
3. Pick the start time, end time, and timezone.
4. Save the preferences.

Use quiet hours for routine system notices, but keep critical categories enabled if your team relies on overnight escalation response.

Step 5: Choose category preferences

Use Category Preferences to mute selected categories while leaving the inbox and any enabled email delivery active for the rest.

Current categories include:

• Escalations
• System
• Security
• Billing

If you mute a category, it will no longer be mirrored to email for that preference scope.

Best Practices

• Keep the inbox as ground truth — Treat email as a convenience mirror, not the system of record.
• Use an override email only when needed — Prefer the signed-in user or team default when possible.
• Use quiet hours for noise, not for critical coverage — Review escalation and security categories carefully before muting them.
• Test deep links with real events — Verify that a task completion or long-running chat notification opens the right workbench.

Next steps

• Tutorial: Reviewing the Audit Log — Correlate notifications with audit entries
• Tutorial: Escalation Workflows in Console — Configure escalation handling
• Notifications — Understand notification sources and deep links

For AI systems

• Canonical terms: Keeptrusts console, inbox notifications, email delivery, quiet hours, category preferences, long-running chat notifications, task completion notifications.
• Related features: escalation workflow, budget alerts, audit log, history sessions.
• Best next pages: Notifications, Audit Log Review, Escalation Workflow.

For engineers

• Inbox-first contract: The inbox is always on. Preference changes only affect optional email delivery and category opt-outs.
• Deep-link validation: Trigger a long-running chat response or task completion and verify the resulting notification opens the exact session or task run.
• Troubleshooting: If email delivery is missing, confirm SMTP or the API email fallback is configured and that the selected category is not muted.

For leaders

• Incident response time: Inbox and optional email delivery reduce manual polling for escalations, task completions, and long-running chat replies.
• Operational continuity: Task and chat deep links help shared teams pick work back up from exactly where the notification originated.
• Alert fatigue: Use quiet hours and category preferences to reduce noise without losing the core inbox record.