Notifications in KAMI Tasks
Two things live under this name: the notifications inbox — everything that happened that involves you — and the preferences that decide how each kind of event reaches you.
Where: Notifications in the main menu You need: nothing beyond your Tasks access
Which mechanism, when
KAMI Tasks can tell you about things three different ways, and they are easy to confuse:
| You want | Use |
|---|---|
| To follow one specific ticket | Watch it, on the ticket |
| To be told about things assigned to you | Your notification preferences |
| To be told whenever a condition is met, across many tickets | An automation |
Watching is per ticket. Preferences are per event kind. Automations are per rule, and reach people who are not otherwise involved.
The inbox
The Notifications page collects what concerns you: assignments, mentions, status changes, comments on tickets you watch. It is the catch-up view for time away — work through it rather than trawling boards to find what moved.
Being notified does not require being the assignee: watch any ticket (Watch options on the ticket page) and its activity reaches you. See Creating and editing tickets.
Choosing what reaches you, and how
In the notification settings you choose per kind of event, with In-app and Email toggled independently, then save.
The split that works for most people: everything in-app, and email only for what would justify interrupting a day off — mentions and direct assignments. That keeps the inbox complete while keeping email meaningful.
If your company has the Slack integration connected, project activity can also flow into Slack channels. That is configured company-wide by an admin, separately from your personal preferences — so turning something off here does not stop it appearing in Slack.
What Happens Next
- Preference changes apply to new events, not to what is already in your inbox.
- Turning off email keeps the in-app record intact — you lose the interruption, not the information.
- Automations reach you through these same preferences, so a rule can fire correctly and still be muted at your end.
Tips
- Turn email down before you turn notifications off. Most notification fatigue is email fatigue; the in-app inbox costs nothing to leave on.
- Watch tickets you care about but do not own. It is the difference between finding out and being told.
- Unwatch when you stop caring. Watched tickets accumulate, and an inbox full of things you no longer need is how people stop reading it.
- If your team is drowning, look at the automations, not at individual preferences. One noisy rule generates more traffic than every personal setting combined.
Troubleshooting / FAQ
Q: I am missing things I should have been told about. Check the preference toggles for that event kind, then check you are actually assigned or watching. Notifications follow involvement.
Q: I get too much email. Turn email off per event kind and keep In-app on. You lose nothing — the inbox still records everything.
Q: I turned a notification off but it still appears in Slack. Slack posting is configured company-wide by an admin and is independent of your personal preferences.