Notifications
Two channels, per-type control, and why muting one does not mute the other.
Two channels
Krrim notifies you two ways, and only two:
| Channel | What it is |
|---|---|
| In-app | The bell, delivered in real time to any open tab |
| Sent to your account address |
The channels are independent. Muting the bell for a notification type does not unsubscribe you from its emails, and unsubscribing from an email does not stop the in-app notification. They are separate switches because people genuinely want different answers for each — a busy type is often worth a bell and not worth an inbox entry.
Set them per type in Settings → Notifications.
What notifies you
- You are assigned a task
- You are @mentioned in a description or comment
- Someone comments on a task you follow
- A task you follow changes status or is updated
- A task of yours is unblocked — the last thing blocking it closed
- A task is due soon
- Work of yours is escalated for sitting too long
One email per save, not one per field
Change five fields on a task and everyone following it gets one email listing the five changes — not five emails.
Your per-type preferences still apply inside that digest: if you have muted status changes but not assignment, a save that did both tells you about the assignment only.
Unsubscribing from email
Every notification email has a one-click unsubscribe. It turns off that type of email and nothing else — your bell notifications keep working, which is almost always what someone clicking it actually wants.
Following
You follow a task automatically when you are assigned it, comment on it, or are mentioned in it. You can follow anything else manually, and unfollow from the task's own menu.
Following is how you get notified about work that is not yours — reviewing someone else's task, or watching something you handed over.