Member notification centre, and an event's origin

Featurekamo-shared-library
Shipped
August 14, 2026 at 6:01 AM UTC
Author
Kamo
Commit
9423cb9

Adds MemberNotification and MemberNotificationPreference: one row per member per notification, because read, dismissed and snoozed are per-person answers and a shared row has nowhere to put them. Preferences cover the two halves separately — mutes, quiet hours and do-not-disturb are applied when the notification is raised; sound, volume and desktop notifications are properties of the browser. CalendarEvent gains SOURCE_TYPE, SOURCE_ID and DEEP_LINK so an event made by a service can lead back to whatever it is about. A lead callback mirrored onto a calendar was previously titled "Lead Callback" and pointed nowhere, so a member looking at it had to go and find the lead by hand. CalendarEventReminderRepository gains per-event lookups and fetches the owning calendar with a due reminder, which is what lets the delivery fan-out ask whether an event belongs to the organisation without a query per reminder. Schema applied by KamoInitializer's MemberNotificationMigration and verified in Yugabyte before this landed.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing