Product helpNotes & docs

Notes & docs

TL;DR

Ripple Notes are lightweight, Notion-style pages for capturing ideas, plans, or documentation. They support markdown formatting, autosave, and real-time collaboration inside the same workspace as your Channels, Jams, and Tasks.

Overview

Notes bridge the gap between conversation and execution. Use them for agendas, meeting prep, strategy docs, brainstorms, or reference material. Because Notes live inside channels, they inherit the same permissions and context links as the rest of your work.

Note

Mirror the copy from Ripple Onboarding Guide — New Zealand Edition 2025 sections 4.1.1.4 (New Note quick-create) and 4.1.6 (middle-panel Notes workspace). Those sections correspond to Version 25.docx pages 8 and 14–15.

In depth

Creating a note

  1. Click + New Note from the sidebar or within a channel.
  2. Add a clear title and choose visibility: Private, Org-private, or Shared (public link sharing coming soon).
  3. Start typing—each line is a block, and / opens formatting commands.

The NZ guide outlines the exact steps (rename Untitled Note, toggle Private vs Public, search within Notes) plus the icon set (Save 💾, Share 🔗, ellipsis ⋯). Link back to section 4.1.1.4 whenever you reference these controls.

Formatting & collaboration

  • Markdown syntax is fully supported (headings, bullets, quotes, code).
  • Autosave keeps edits instant; no manual save buttons needed.
  • Multiple users can edit simultaneously with presence indicators.
  • Add comments, tag teammates, or link tasks inline.

Use section 4.1.6 for the layout description: search bar, Private/Public groupings, Add Note block, Save/Share/Ellipsis actions, and access settings (People with Access + General Access).

Integration with Ripple workflows

  • Attach critical Notes to a Jam as pre-read resources.
  • Reference Notes inside Call summaries for richer follow-up.
  • Convert Note bullets into Tasks with /convert.
  • Lean on AI summaries to scan long Notes quickly.

Context panel reminder

The right-hand panel behavior described in section 4.3 applies to Notes as well—participants, Invite (+), Details, Files, and Activity feed live there. Cite that section when you show screenshots or run enablement sessions.

Best practices

  • Use consistent titles (“Board Pack – Q1”, “Growth Plan – FY25”) for easy search.
  • Store key docs in channels tied to strategic themes.
  • Tag related Notes to build a narrative chain across projects.

See also