The console has no notifications #168

New Issue

2026-10-06T08:12:34Z

cgalo5758 commented

2026-10-06 08:12:34 +00:00

The question

The console tells a person something only on the page where it happened, and only while they are looking. None of these reach anyone:

a site request declined a few seconds after the member left the page;
an integration that stops answering;
a member's payment that fails;
an invoice that goes overdue.

Most platforms keep notifications behind a control in the top bar, with read and unread state. What does the console notify about, whom, and where are notifications read?

What depends on the answer

The outcome of a person's own request that finishes later is a notification, because they may have left the page before it finished. A notice on the page is not enough on its own.
A response shown right where an action was taken is not a notification.
A condition that stays wrong until someone fixes it is an attention item (#78), and a notification can link to it.
#167 decides how a notice looks, and notifications need the same part.
Whether anything leaves the console, by email or another channel, is part of the same question.

Options known so far

Notifications for each person behind a control in the top bar, with read and unread state, fed by kinds of event registered in one place.
The same, plus email for kinds that cannot wait.

Decided when

The kinds of event that notify, who receives each, and where notifications are read are written down, and #78 and #167 say how they relate.

## The question The console tells a person something only on the page where it happened, and only while they are looking. None of these reach anyone: - a site request declined a few seconds after the member left the page; - an integration that stops answering; - a member's payment that fails; - an invoice that goes overdue. Most platforms keep notifications behind a control in the top bar, with read and unread state. What does the console notify about, whom, and where are notifications read? ## What depends on the answer - The outcome of a person's own request that finishes later is a notification, because they may have left the page before it finished. A notice on the page is not enough on its own. - A response shown right where an action was taken is not a notification. - A condition that stays wrong until someone fixes it is an attention item (#78), and a notification can link to it. - #167 decides how a notice looks, and notifications need the same part. - Whether anything leaves the console, by email or another channel, is part of the same question. ## Options known so far - Notifications for each person behind a control in the top bar, with read and unread state, fed by kinds of event registered in one place. - The same, plus email for kinds that cannot wait. ## Decided when The kinds of event that notify, who receives each, and where notifications are read are written down, and #78 and #167 say how they relate.

cgalo5758 added the

kind

design

area/operator-ui area/member-ui labels 2026-10-06 08:12:35 +00:00

cgalo5758 referenced this issue

2026-10-06 08:12:40 +00:00

The operator has no single place showing what needs attention #78

cgalo5758 referenced this issue

2026-10-06 08:12:40 +00:00

Alerts are written by hand in about twenty variants, and the design system has no part for a notice #167

cgalo5758 referenced this issue

2026-10-06 18:11:55 +00:00