Notifications

Automation nobody is watching is a queue that grows quietly. CodeBook has three ways to make sure somebody knows.

Per-station email

Notify by email in the station's settings takes one address. When a card arrives on that station, that address is emailed.

Where it matters most:

• Approval stations — the person deciding needs to know something is waiting.
• Escalation stations — a card here has already failed more than once.
• Human stations — the same reason, one step earlier.

Where it usually does not: stations whose worker acts immediately. An email for every card entering Development is noise, and noise trains people to ignore the ones that matter.

The shared inbox

CodeBook's in-app notifications go to the Bookbag inbox — the same bell in every product in the suite. A notification links back to the thing that raised it, so opening one from another product brings you here.

Mentions

Mentioning somebody in a card's discussion notifies them. This is how a worker's question reaches a specific person: the agent asks, you see the mention, you answer in the thread. Name the agent in your answer (@ and its name) and it picks the answer up: inside its run if one is going, or as a reply if not.

A note on quantity

Every notification you add makes the others slightly less likely to be read. The teams who get the most out of this feature use it on two or three stations: the one where somebody must decide, and the one where things land when they have gone wrong.