KamoCRM

The member who caused a notification opens their card from it

Featurekamo-internal
Shipped
September 23, 2026 at 9:26 AM UTC
Author
Kamo
Commit
53f99a4

"Dana Reyes dealt you in", "Weekly sync · Dana Reyes", an unread-chat card whose body is the sender: EmailService (29cb21e) now sends actorMemberId (as text) and actorName, the name exactly as the title or body spells it, and the bell draws that stretch of text as the member's name. - NotificationText cuts the name out of the title (else the body) once, at its first occurrence; everything else reads exactly as before. Used by the toast, the history row (clickToggles={false}: the row opens the notification) and the detail dialog. - A toast's card opens at the deck's level. MemberHoverCard/MemberName take zIndex, and the toast passes NOTIFICATION_DECK_Z (1500, now one constant with the deck's own). At the card's 1305 it opened underneath the deck it came from; at the same level it paints over it (it is appended to <body> later) and still under its own tooltips (appended later still). - UnreadChatNotifier sends the sender as the actor, never for Exec2Exec. The server also keeps an actor on /self only from the caller's own organisation. - Spec "As built": the notifications paragraph. Verified: tsc; eslint (nothing on changed lines); the repo's 19 guards; vitest (notifications, members, lib, settings, chat; the few that timed out under machine load pass on their own); and a Chrome probe that the name stays inline in the toast's two-line clamped title and the history row's ellipsis still holds.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing