Notification settings
Notification settings control which events trigger emails and alerts — what KAMI sends automatically, and to whom.
Where: My Team › Settings › Communication › Notifications You need: the notifications right
Why this is worth tuning
Notifications are the main way KAMI tells someone that something needs them: a request to approve, a document to sign, a change to review.
Both failure modes are expensive:
- Too few, and requests sit unactioned because nobody knew — the approver genuinely was
not told.
- Too many, and people filter KAMI email to a folder, after which they are not told
either. This is the more common failure, and it looks like nothing is wrong.
The test to apply
For each event, ask: could the recipient do something about it?
If yes, notify. If it is informational, it probably belongs on a dashboard rather than in an inbox — the queues on the My Team dashboard already show people what is waiting on them without anything being sent.
Approvals depend on this
The most consequential notifications are approval ones. An approval route that works perfectly still stalls if the approver is never told there is something waiting.
When requests are sitting unactioned, check both: is the route pointing at the right person, and are they actually being notified?
When to revisit
- After a reorganisation — people who changed role may now get, or miss, the wrong things.
- When someone says they were never told — usually a settings problem rather than a
personal one, and usually true for others too.
- When people mention KAMI email volume — a signal they are close to ignoring all of it.