Notifications & the Decision Feed
How KeyOne keeps you aware of what’s changing — the always-on Decision Feed bar, what its counts and status dot mean, and how to act on what it surfaces. About 5 minutes.
KeyOne doesn’t rely on you remembering to check in. The Decision Feed keeps a live pulse of your open work visible at all times, so nothing important sits unseen.
The Decision Feed bar
Running along the bottom of the app is a persistent strip — the Decision Feed. It’s visible wherever you are, and it answers one question continuously: what’s open right now?
It shows live counts of your:
- Risks — open exposures the engine has detected
- Decisions — open upside the engine has found
- Tasks — open actions waiting to be done
The feed refreshes itself roughly every minute, so the numbers stay current without you reloading anything.
Reading the status dot
Next to the Decision Feed label sits a small status dot that tells you the health of the feed:
| Dot | Meaning |
|---|---|
| Green | Live — counts are current and the engine is responding. |
| Yellow | Loading — the feed is fetching or refreshing. |
| Red / degraded | The engine routes are still initialising or temporarily unavailable. |
Honest behaviour: if the engine is still warming up, the feed says so plainly (for example, “engine routes initialising”) rather than showing stale or invented counts. A degraded feed is a status, not data you should act on as if it were live.
From a count to an action
The Decision Feed is a doorway, not a dead end. The flow is always the same:
- Notice a count climb in the feed (say, risks tick up).
- Open the Work Queue (sidebar → Core → Work Queue) to see what’s new.
- Triage and act using filters, summary pills, and bulk actions. (See Decision Inbox & Win List.)
Worked example (illustrative). You’re reading a Category Share hub when the feed’s risks count jumps from 6 to 9. You open the Work Queue, click the Critical pill, and find three new OOS risks at a single retailer’s stores worth a combined R 0.9m / week in exposure. You bulk-assign them and move on. Numbers are illustrative.
Hub-level decision counts
You don’t only see decisions globally. Every hub carries its own Decisions & Actions panel showing the open risks, decisions, and tasks for that area, with a “View all in Work Queue →” link. So if the global feed tells you risks are up and you suspect it’s an availability problem, open the OSA hub and its panel will confirm whether that’s where the new items landed. (See Using a Hub.)
What KeyOne does not (yet) do
In the spirit of honesty:
- There is no email / SMS / push notification system to document as a live feature today. The Decision Feed is the in-app awareness mechanism; don’t expect KeyOne to email you an alert yet.
- Configurable alert thresholds (e.g. “notify me when exposure exceeds R X”) are not a finished, self-serve feature. If a guide elsewhere mentions thresholds aspirationally, treat the in-app Decision Feed and Work Queue as the real, current way to stay on top of things.
If you don’t see a notification control somewhere, it genuinely isn’t there yet — KeyOne won’t pretend otherwise.
Tips
- Keep one eye on the dot. A green dot means the counts you’re trusting are live.
- Treat a rising count as a prompt, not an interruption. Finish your thought, then open the Work Queue.
- Use hub panels to localise. The global feed tells you that something changed; hub panels tell you where.
Next: Using a Hub