Notes

Notes at /app/notes use the Tiptap rich-text editor: headings 1-3, bullet and ordered lists, blockquote, code blocks (with monospace), inline code, links, bold/italic/underline/strike, and inline images. Tables are queued — see /roadmap.

Notes autosave as you type. The save indicator at the top of the editor tells you the current state (saved / saving / unsaved). If you lose connection mid-edit, the editor keeps your local changes and re-syncs when the connection comes back.

Each note has a visibility toggle: **Private** (only you can see it) or **Org-wide** (every workspace member can read it). Org-wide notes are the right choice for SOPs, runbooks, and onboarding docs that you want to outlive any one person.

Visibility can be flipped at any time from the note header. Toggling a private note to org-wide does NOT email the team — they’ll see it on their next visit to /app/notes.

The note index at /app/notes shows every note you have access to (your private + the org-wide ones), sorted by most recently edited. The card preview is plain-text — tags and HTML entities are stripped so the preview reads cleanly regardless of how the note was authored.

Notes are also indexed in the global command palette (⌘K). Searching for any text matches against note titles and bodies. Hitting Enter on a result jumps you to the note.

There’s no separate "wiki" module — org-wide notes ARE the wiki. Pin the most-referenced notes (an SOP, the company handbook, the customer escalation playbook) at the top of /app/notes by toggling "Pin to top".

For pages that benefit from a running structure (engineering team docs, marketing campaigns), create a top-level note for the section and link to other org-wide notes from inside it. Tiptap supports inline links and renders them as clickable.