Request · review · decide
Approvals that leave a trail
Ask the right person to sign off on any document, and keep the answer where the document is — not in a mail thread nobody can find later.
✅ Approvals
Request sign-off on any document of the mesh.
Any node can carry approvals: a Request Approval entry on the node's menu, an inline Approvals section on the markdown overview, and Approve/Reject views for the designated approver. Decisions dispatch a notification to the requester and write an activity entry on the document — the sign-off trail lives beside the content it signs off, as _Approval satellites of the node.
What ships
Approvals/Approval— the satellite type: the record, its Overview with Approve / Reject for the named approver, and the compact Thumbnail card.Approvals/Desk+ theApprovals/Workspaceinstance — the document-anchored surfaces (request form, inline list). One instance serves every document on the mesh, addressed per render, so nothing is registered onto any other node's hub.- A
UiContributionnode — the Request Approval menu entry, contributed as data: installing or removing this package adds or removes it, with no platform build. - Data that outlives the UI — the
Approvalrecord and the_Approval→annotationssatellite mapping are platform-level, so approvals keep deserializing and routing wherever this package is not installed.
Contents
Where to start
- Approval Desk — every request that concerns you, waiting or decided. This is the package's front door.
- Request approval — the ✅ action on any document node; it writes the
_Approvalsatellite and notifies the approver.