Skip to main content
The Notes Library at /dashboard/notes is shared by your organization. Operator and higher roles can read it and edit it with the existing engagement-edit permission. An active read-only engagement membership in your organization makes library changes unavailable. Engagement, host and port notes remain separate; library notes do not automatically become findings, evidence, reports or published content.

Browse and organize

Open Notes Library in the sidebar. Open a folder to browse its immediate items; Parent folder and Library root move back up. New folder creates a folder draft; Folder parent moves it when you explicitly save. New note opens a plaintext draft in the current folder. Duplicate titles are allowed. Destination selectors include the stable folder identifier when titles are duplicated, so identical names remain distinguishable. New note and New folder are unavailable while the selected destination or any ancestor is archived or unavailable; return to Library root or restore the hierarchy first. A folder must have no active immediate notes or child folders before it can be archived. Show retained archives lets you open archived note bodies without restoring them. The catalog lists metadata; a saved body is loaded only when you open that note. Opening requires fresh access and matching saved metadata, and Cancel opening note leaves the catalog usable. Archive retains each item’s content and individual state. Restore requires active ancestry; Restore folder at root or Restore note at root is the explicit alternative when the old parent is unavailable. Restoring a folder does not restore its individually archived children.

Write and preview

Use the labelled Note title and native Note body textarea. Titles contain 1–100 characters after trimming. Bodies retain plaintext whitespace and are limited to 128 KiB of UTF-8 bytes; the editor displays the byte count. Note folder changes the destination on Save. Select Preview language for an adjacent syntax-highlighted preview, using the bundled language list or Plaintext. The preview runs in a local Worker with no automatic language detection or server preview request. HTML remains escaped text; notes are never executed. A failed or timed-out preview retains the editable plaintext. An unknown saved language falls back to plaintext. Save note is explicit. Typing while a save is pending remains in your draft after acknowledgement. Cancel and discard draft is the deliberate way to discard unsaved changes. An ordinary in-app link asks for confirmation while the note is dirty; declining keeps the exact draft. Reloading or closing the tab uses the browser’s native unsaved-changes warning. Accepting a leave discards the draft; changes are not autosaved or persisted outside the editor. Closing the editor is required before opening another draft. Archived bodies and a read-only library remain readable without write controls.

Recover a conflict or uncertain result

A save uses the record’s saved version. If another session changed the record or hierarchy, your draft stays intact. Choose Refresh saved data to obtain a fresh catalog and the selected note’s saved body. Only a matching organization, note ID and saved version can be adopted; another note’s response or an older acknowledged version cannot replace the draft. Refreshing does not overwrite your draft. Then deliberately choose Adopt fresh saved note to replace it, or Keep draft and retry against fresh version after reviewing the newer baseline. Folder recovery follows the same explicit process. A refresh failure leaves recovery unavailable and keeps your draft. If a create outcome cannot be confirmed, another create attempt is blocked. Refresh and review the catalog for a possibly saved item; no match is inferred and rollback is not claimed. You can cancel the draft and open a saved item, or explicitly confirm that you reviewed saved items before allowing a new create attempt. Retrying may create a separate item. Review this choice carefully.

Availability

The Notes Library merged into development through PR271 on October 11, 2026. Development acceptance includes all three authenticated Notes browser cases: explicit saved content and escaped syntax highlighting, shared editing/conflict recovery with User denial, and retained archive/restore hierarchy. This records development delivery; Production deployment availability has not been established.