Reviewing Proposals
Approve, edit, or reject captured changes in Slack before they reach your docs.
Captured knowledge always passes through review before it's saved. A reviewer approves, edits, or rejects each proposed change, so your documentation only ever gets updates someone has signed off on.
Review in Slack
Captures from /docpipe and watched channels post an approval card titled "Documentation update needs approval." For each proposed change, the card shows:
- the target document — with its space and section,
- a before-and-after of the exact edit,
- a short rationale and a confidence score.
Approve, edit, or reject
Each change has three buttons:
- Approve — apply the change to the document as proposed.
- Edit — open the Edit proposal form, adjust the wording, and choose Save & approve to apply your edited version.
- Reject — discard the change.
When a capture produces several changes at once, you'll see a single plan card with Approve plan and Reject plan.
After you act, the card is replaced with a record of what happened — ✅ Approved, ✏️ Edited, or ❌ Rejected, along with who did it — so the Slack thread keeps an audit trail.
For a watched channel, the card is sent as a DM to that channel's approver, so proposals land with the right person automatically. For a /docpipe capture, the card appears in the channel where the command was run, and anyone there with permission can act on it.
Some high-confidence captures skip the card entirely and are applied automatically, with a confirmation posted in their place — see How proposals work.
Reviewing regularly is what keeps captured knowledge trustworthy. A short, routine pass through pending proposals — approving the good ones and fixing wording where needed — usually takes a few minutes, and it's what lets your team rely on the answers Docpipe gives.
Voice notes
Voice notes you record are reviewed under My Notes: check the transcript, then File into docs to send it through the same proposal flow, or Dismiss it. See Voice capture.
Other things that need review
Captures aren't the only things that reach a reviewer. Proposed updates from connected tools (GitHub, Jira, and Linear) and documents due to be re-verified appear in the Review queue, where you review them inside the document with a full redline. Those are covered in Governance & knowledge health.