Help & Reference

Glossary

What the key terms mean.

The vocabulary Docpipe uses, in one place.

  • Organization — your workspace. The outer boundary; members of one organization never see another's content.
  • Space — a top-level area of your knowledge base (Engineering, Handbook, Ops). Access is granted per space. See Space access.
  • Section — a group of documents within a space.
  • Document — a single page of knowledge, made of blocks. See Working with documents.
  • Block — the unit an editor document is built from: a paragraph, heading, list, table, image, and so on. See The editor.
  • Draft / Active / Archived — a document's status. A draft is private to its author; active is published to the space; archived is set aside but not deleted.
  • Capture — turning knowledge from Slack, a voice note, or a personal note into a proposed document update. See Capturing knowledge.
  • Proposal — a suggested change to your docs, from capture or an automated review, waiting for someone to approve or reject it. See How proposals work.
  • Review inbox — the queue of documents waiting on you, to verify or to accept a proposed change. See Verification & staleness.
  • Verification — confirming a document is accurate today. Verified documents show a badge; changes send them back for re-confirmation.
  • Expert (SME) — a subject-matter expert assigned to a space, who unanswered questions are routed to. See Experts & SMEs.
  • Access level — a member's rights within a space: Viewer, Editor, or Admin.
  • Role — what a member can do at the organization level (managing members, integrations, settings), separate from space access. See Roles & privileges.
  • Knowledge Health — the dashboard of what's overdue, unowned, or unverified across your knowledge base. See Knowledge health.
  • Watched channel — a Slack channel Docpipe monitors for knowledge worth capturing. See Watched channels.
  • Escalation — a question your docs couldn't answer, routed to a space's expert.
  • Embedding — a numeric representation of your text that powers search and AI answers. See AI & your data.
  • MCP server — the read-only endpoint that lets AI clients (Claude Code, Cursor) reach your knowledge base. See MCP server.
  • API key — the credential an MCP client uses to authenticate. See API keys.