Notifications exist so you need not monitor progress constantly. Configure them under Settings → Notifications.
Channels
| Channel | Suitable for |
|---|---|
| In-app | All items; the full record |
| Items needing action within the day | |
| Chat | Team-visible events — see Chat platforms |
| SMS | Only genuine urgent matters |
| Push | Mobile follow-up |
What deserves to be notified
The important events are those where work has stalled and cannot proceed without you:
- a task posing a question (
NEEDS_HUMAN_REVIEW) - a plan awaiting approval
- a pull request ready for review
- a task that failed
Everything else is purely informational. Sending a notification for every status change causes people to ignore them, including the one that truly matters.
Personal and organisational settings
Channel configuration is organisational; which events reach you is personal. Enabling Slack for the team does not determine what alerts you individually.
Chat channels
Where a chat platform is linked, notifications can be sent to a channel instead of individuals — which is usually appropriate for "a pull request is ready" but usually unsuitable for "your task is posing a question".
Team-visible events belong in channels. Personal actions should go to personal notifications; otherwise they become everyone’s problem and thus nobody’s.
Terms and account notices
Some notifications are non-negotiable — changes to terms of service and account security notices reach you irrespective of your preferences.
When no notifications arrive
Check in this order: whether the event is enabled for your account, whether the channel is linked at the organisational level, and whether the delivery log shows an attempt. For chat platforms specifically, delivery may fail if the bot has been removed from a channel — which appears identical to no notification being sent.