Notifications
How KeyOne tells you what changed — the bell and the inbox, which events reach you immediately and which arrive in a daily digest, and how to change that per event. About 4 minutes.
KeyOne raises decisions continuously. Notifications are how the ones that need a person reach you without you having to go looking.
The bell and the inbox
The bell in the top bar carries a count of unread notifications and opens a short list of the most recent. View all notifications → at its foot opens the full inbox at /app/notifications, which is the complete history rather than a preview.
Every notification carries the same four things:
- What happened — a title written for a reader, not a machine. A failed rule is named by its rule name, not its YAML id.
- Who or what it concerns — the outlet, product or account involved.
- A value, where the event has one.
- A link to the thing itself. Every notification leads somewhere: an assigned decision opens that decision, a failed run opens Run history, a security alert opens the Audit log.
What KeyOne notifies you about
Seven event types, each with its own delivery setting:
| Event | What it means |
|---|---|
| Decision assigned | Someone assigned a decision to you. |
| High-severity decision | The engine raised a decision at high or critical severity. |
| Campaign deadline approaching | A campaign you are part of is nearing its end date. |
| Campaign completed | A campaign finished, with its final result. |
| Run failed | A scheduled rule or engine run failed. Admins only. |
| Session token replayed | A refresh token was presented after it had already been rotated. The session is revoked automatically and admins are told. Admins only. |
| Open work digest | A periodic summary of what is still open and assigned to you. |
Immediate, or once a day
Each event is delivered one of two ways, and you choose per event in Settings → Notifications:
- Immediate — sent as it happens. The default for anything that may need action now: an assignment, a high-severity decision, a failed run, a security alert.
- Daily digest — rolled into one message a day. The default for the things that read better together: campaign progress and your open-work summary.
Setting an event to digest does not silence it; it changes when it arrives. The in-app inbox receives every event either way, immediately.
Immediate events are also sent by email, and the digest is an email by definition. Every non-transactional message carries a working unsubscribe link.
Whether email actually leaves the building depends on how the deployment is configured — a deployment with no mail provider set up logs the message instead of sending it, and says so rather than reporting a delivery that did not happen. Ask whoever runs your instance which it is.
Decisions on a hub
Notifications are not the only route to open work. Every hub carries its own list of the decisions raised in that area, so you can go from “something changed in availability” to the specific cards without leaving the hub. Notifications tell you that something needs you; the hub tells you where it sits. See Using a Hub.
What KeyOne does not do yet
- No SMS or push. In-app and email are the two channels.
- No configurable thresholds. You cannot yet say “tell me when exposure passes R X”. Severity is set by the decision definitions, not per person.
- No per-recipient routing rules beyond the immediate/digest choice above.
If a control is not in Settings → Notifications, it is not there yet.
Next: Using a Hub