- Shipped
- August 22, 2026 at 8:50 AM UTC
- Author
- Kamo
- Commit
- 48cde37
A master note is the one note a member — or an organisation — always has. "My Master Note" is provisioned per membership; "Our Master Note" is one per organisation and appears on every member's launchpad. Both are ordinary `notes` rows carrying a MASTER_SCOPE, not a new table, so the Lexical editor, autosave, versions, colours, the floating sticky and the RAG publish all keep working with nothing to keep in step. An ORG row carries a NULL MEMBER_ID on purpose: every member-scoped finder matches `n.member.id = :memberId`, so the organisation's note can never be returned by one member's private listing, update or delete. Reads that should see it go through the new `…VisibleToMember` finders, which widen to it explicitly; writes keep the member-scoped pair and so cannot reach it at all. MANAGE_ORG_MASTER_NOTE (228) is a standalone root with a null serviceType, following MANAGE_ORG_BRANDING: the role, job-title and department editors only render a service's section when the org has that app enabled, and the org master note is on every launchpad whether or not Notes is switched on. Not parented to VIEW_NOTES for the same reason — KBService serves the note without a notes right.