Notifications, Inbox, and sender trust

Configure how information reaches you, then test the actual destination. Notification preferences and channel sender access solve different problems.

Notification delivery

Open Settings → Notifications. Set minimum severity, quiet hours, and mute state. Quiet hours use the time convention shown by the control. Mute all suppresses notifications regardless of their per-kind rule.

Use the per-kind matrix for immediate delivery, badge-only display, digest batching, or never. Conditions can escalate relevant items to immediate delivery but cannot revive events suppressed by the global settings. Review the destination as well as the delivery mode.

Read the notification list

Open Notifications to inspect unread events, follow their links, acknowledge items, or delete entries you no longer need. Clearing an alert does not resolve an underlying task or grant approval.

Inbox preferences

Use Inbox settings for source behavior, cleanup, retention, and the triage controls offered by the current runtime. Check muted threads if expected material is absent. Review generated drafts as your own outgoing communication before sending.

Sender trust

Settings → Sender trust shows who may talk to the agent through a connected messaging channel. Review the sender identity and channel before granting or revoking access. Unknown-sender approvals and pairing are access decisions, not ordinary chat replies.

Self-hosted operators can mint a pairing code with gideon pair <channel>. Hosted customers should use the connection and approval flow available in their account.

Diagnose missing alerts

Inspect the underlying run or Inbox item first. Then check source access, silent-job behavior, severity, quiet hours, per-kind rules, and the configured delivery target.