Your inbox

Select the bell in the top bar to open your notifications. Each notification can be marked read (Mark as Read) or dismissed (Dismiss), and Mark All as Read clears the unread count. Preferences takes you to your notification settings, and View All Alerts opens the Alerts page.

Notifications are personal: marking one read or dismissing it changes only your inbox.

Choose how notifications reach you

Go to Settings, then Notifications. Every change saves straight away.

Presets

Pick one of three presets to set your defaults in one click:

If your settings don't match a preset, Kumo.io shows that you have a custom setup; pick a preset to reset it.

Per-notification controls

Open Advanced — per-notification channel controls to set each kind of notification separately for In-App, Email and Slack. The Everything row is the default; a setting on a specific kind overrides it.

Each cell takes one of these settings:

Critical events skip quiet hours and severity thresholds, but never override Muted or Off.

Sync succeeded is off in your inbox until you turn it on, so a healthy schedule of syncs doesn't flood it. Sync failed is on by default.

Delivery windows (email and Slack)

Under Delivery windows:

• Turn on Quiet hours and pick the hours it runs from and to. During quiet hours, non-critical email and Slack notifications are held for your next digest instead of being sent straight away. Critical alerts still come through immediately.
• Set the Digest to daily or weekly, and the hour it's sent. Notifications set to Digest are batched into that one message.

Hours are in your browser's time zone. Choose Save Windows to keep your changes. Your inbox isn't affected by quiet hours or digests; notifications appear there straight away unless you have muted them for In-App.

Subscriptions

Subscriptions lists any subscriptions you have, with their channels and minimum severity. Choose Remove to end one. Without subscriptions, you receive notifications according to the settings above.

Test it

Choose Send Test Notification, then open the bell to see it arrive.

Hosted and self-hosted

• Email: on kumo.io, Kumo.io sends email for you. On a self-hosted installation, email notifications need an email relay. See How do I configure email (self-hosted)?
• Slack: Slack delivery needs Slack connected to your account, which is part of the Business plan. See How do I connect Slack?

Which plans include notifications

Your inbox and notification settings are available on every plan. What arrives depends on what your plan produces: alert notifications need alert rules, and report notifications need reports, both part of the Business plan. See How do I get told when something important changes? and What does each plan include?

From the CLI (self-hosted)

On a self-hosted installation, run these on the installation:

kumo notification list
kumo notification unread-count
kumo notification mark-read <id>
kumo notification mark-all-read
kumo notification dismiss <id>
kumo notification preferences show | set
kumo notification subscriptions list | create | test
kumo notification delivery list | show <id> | retry <id>
kumo notification diagnose <notification-id>

Run kumo notification <command> --help for each command's options. To add a subscription, use kumo notification subscriptions create --kind <kind> --channel <channel>, with --workspace <id> to limit it to one workspace (otherwise it covers the whole account) and --min-severity <level> (default info). These commands don't run against kumo.io.