The console has no notifications #168

Open
opened 2026-10-06 08:12:34 +00:00 by cgalo5758 · 2 comments
Owner

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-uiarea/member-ui
labels 2026-10-06 08:12:35 +00:00
Author
Owner

The notice part (#167) keeps no record of closed notices. A notice's close button posts to whoever owns the fact, and the owner records it on its own row.

One of today's two closable notices belongs here. A declined or failed site request's outcome on the FedWiki sites card is closed by setting acknowledged_at on the lifecycle request (AcknowledgeLifecycleRequest in internal/integration/lifecycle.go). By this issue's own rule that outcome is a notification, because the member may have left the page before it finished. When notifications have their store, closing the outcome becomes marking it read there, and that read state replaces acknowledged_at.

One difference to settle here: acknowledged_at is kept per workspace, so one member closing the outcome closes it for everyone in the workspace, while a notification's read state is per person.

The notice part (#167) keeps no record of closed notices. A notice's close button posts to whoever owns the fact, and the owner records it on its own row. One of today's two closable notices belongs here. A declined or failed site request's outcome on the FedWiki sites card is closed by setting `acknowledged_at` on the lifecycle request (`AcknowledgeLifecycleRequest` in `internal/integration/lifecycle.go`). By this issue's own rule that outcome is a notification, because the member may have left the page before it finished. When notifications have their store, closing the outcome becomes marking it read there, and that read state replaces `acknowledged_at`. One difference to settle here: `acknowledged_at` is kept per workspace, so one member closing the outcome closes it for everyone in the workspace, while a notification's read state is per person.
Author
Owner

Toasts are a third way the console tells a person something, beside notices (#167) and notifications, and this issue has to place them too. Today there are two:

  • an error toast, shown by internal/embeds/static/error-handler.js when a request fails;
  • a success toast, shown by internal/embeds/static/success-toast.js from an HX-Trigger header (showSuccessToast) or rendered into a page that loads after a create.

Both reach only the person on the page, at that moment, and they leave no record. The notice part keeps them a separate part: one shared template for their markup in every layout, and the error toast staying until it is closed.

Questions this issue has to answer about them:

  • Does a notification that arrives while the person is on a page also show as a toast?
  • Is a failure that today only toasts, such as a server error on a save, also recorded so the person can find it later?
  • Which events get a toast, which get a notification, and which get both? These should be registered in the same place as the kinds of event that notify.
Toasts are a third way the console tells a person something, beside notices (#167) and notifications, and this issue has to place them too. Today there are two: - an error toast, shown by `internal/embeds/static/error-handler.js` when a request fails; - a success toast, shown by `internal/embeds/static/success-toast.js` from an `HX-Trigger` header (`showSuccessToast`) or rendered into a page that loads after a create. Both reach only the person on the page, at that moment, and they leave no record. The notice part keeps them a separate part: one shared template for their markup in every layout, and the error toast staying until it is closed. Questions this issue has to answer about them: - Does a notification that arrives while the person is on a page also show as a toast? - Is a failure that today only toasts, such as a server error on a save, also recorded so the person can find it later? - Which events get a toast, which get a notification, and which get both? These should be registered in the same place as the kinds of event that notify.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#168