FAQ

How is Docpipe different from a regular wiki?

A wiki holds whatever you remember to write and update. Docpipe is built to keep your knowledge current: it captures knowledge from where work happens, proposes updates when a PR or ticket ships, and tracks which documents are still trustworthy. You still write the docs — Docpipe helps them not go stale.

Do I have to use Slack?

No. Slack is a convenient way to capture knowledge and ask questions without leaving the conversation, but the web app is fully featured on its own.

Who can see my documents?

Access follows the space a document lives in — members with access to that space can read it, and drafts are private to their author until published. See Access controls and Space access.

Can I edit a document I didn't create?

Yes — if you have Editor or Admin access to its space. You don't need to be the author. See Document lifecycle.

How does the AI avoid making things up?

Answers and proposals are grounded in your documents and come with the sources they used, so you can verify them. And AI-proposed changes are never applied on their own — a person reviews and approves them.

What is my content used for by the AI?

Your documents and prompts are sent to OpenAI to generate answers and embeddings, always scoped to your own organization. See AI & your data for the details and limits.

What happens when I hit a plan limit?

Nothing is deleted. Docpipe shows an upgrade prompt telling you exactly which limit you reached; your existing documents stay exactly as they are. See Plans & usage.

Can I use Docpipe from my code editor?

Yes — connect the MCP server to Claude Code, Cursor, or any MCP client to ask and search your docs without leaving your editor.

My Slack message didn't create a document — why?

Capture doesn't write documents directly; it drafts a proposal for review. Check the Review inbox to approve it.