Monitoring
In-app alerts
The record of what happened on the account, which is why it is the one channel you cannot switch off.
The feed inside the console shows every event on the account, with read state per person, so two people looking at the same account do not clear each other’s badges.
It is listed in the notification settings so the screen can show it, but it is never stored as a preference and never switched off. The feed is the record of what happened, and an account that turned it off would be asking the product to forget things rather than to stop interrupting them. Email and Slack are the channels for controlling interruption.
It is worth being clear about what it is not. The feed answers what happened; the attention queue answers what is still true and unresolved. They are built from different sources on purpose, because a work list derived from an event stream loses a task the moment somebody marks it read.
One narrow exception exists in the permission model for it. Read-only members cannot write anywhere on the platform, except to mark their own notifications seen or read, because a badge somebody cannot clear is not a badge.