Question 1

How do AI-generated doc PRs get into DraftView?

Accepted Answer

Connect the GitHub App to your organization once. After that, every documentation PR in a connected repo (public or private) lands automatically in a shared review queue with its own lifecycle state, so nothing gets pasted in by hand and nothing falls through. You can still load any individual public PR by URL when you just want to try it.

Question 2

Do my reviewers need a GitHub account?

Accepted Answer

No. Reviewers join your organization by email with a magic link and start reviewing right away, with no GitHub account or password. A GitHub-linked teammate then pushes their feedback upstream under a real account, so every suggestion stays properly attributed. For one-off outside reviewers like legal counsel or localization, you can also share a password-protected external link.

Question 3

How does DraftView know which PRs were written by AI?

Accepted Answer

DraftView reads signals from the PR itself: the author, branch name, description, and commit trailers. Detection is generator-agnostic, so it works whether the docs came from Claude Code, Copilot, Cursor, or an in-house pipeline, and it is held to a strict precision bar before a label ever drives a filter or a metric. The label flags a PR for human review. It never blocks or merges anything on its own.

Question 4

What happens after a reviewer requests changes?

Accepted Answer

Their comments and edits sync to GitHub as native review threads and Suggested Changes, so GitHub stays the single source of truth. When the agent pushes a new commit, the addressed view shows the before and after of the exact region they commented on, so the reviewer can confirm the feedback was really handled, not just that a line moved.

Question 5

Does DraftView replace GitHub, or lock us in?

Accepted Answer

Neither. GitHub still owns your content, your comments, and the merge button. DraftView sits on top as a review layer you can add or remove at any time, and it never auto-merges. The one thing we keep that GitHub does not produce is the human-oversight record.

Question 6

Can DraftView prove a human reviewed the AI's work?

Accepted Answer

Yes. Every sign-off writes an append-only record of who reviewed, what changed, how long they spent, and against which version. You can export a per-PR oversight audit, and the dashboard reports the share of AI doc PRs that received a substantive human review versus those rubber-stamped. That is the evidence a green checkmark cannot give you, framed around EU AI Act Article 14 human oversight.

Question 7

Can DraftView actually block a PR from merging until a human reviews it?

Accepted Answer

Yes, on the Team plan and above. DraftView posts a draftview/human-review status check on every doc PR in the queue: pending until a maintainer signs off, green once they do. Mark it a required check in your branch protection rules and GitHub will refuse to merge AI-generated docs that no human has approved. And the sign-off stays fresh: if the agent pushes another change to the docs after approval, the check flips back to pending and the reviewer is asked to look again; a trivial rebase or code-only commit carries the approval forward.

Question 8

Is DraftView free for open-source projects?

Accepted Answer

The Team plan is free for genuinely community-run open-source repos: public, OSI-licensed, and not the documentation of a commercial product. In return, your project links back to DraftView in one way of your choosing: a README badge, a link on your docs site, or DraftView-powered “Edit this page” links. Apply from your org settings: the link-back and license are verified automatically, and a human on our side approves each grant, so an enterprise publishing its product docs under an open-source license still uses a paid plan. OSS grants cover Team features only; Governance (audit exports, oversight metrics, compliance webhooks) is never part of the grant. If your request is declined and you believe that's a mistake, email ossgrant@draftview.app.

Question 9

Which documentation formats are supported?

Accepted Answer

We currently support standard Markdown, MDX and AsciiDoc. AsciiDoc renders correctly, however some features may not be fully functional. We are actively working on improving AsciiDoc support. If you have specific format needs, please contact us to discuss how we can accommodate your workflow.

Question 10

We use X platform for documentation. Can I still use DraftView?

Accepted Answer

We support Docusaurus, Mintlify, GitBook, Hugo, MkDocs, and any other platform that uses a GitHub-based workflow. As long as your files are in a GitHub repository, we can render the preview.

Question 11

We use GitLab/Bitbucket. Can we still use your visual review engine?

Accepted Answer

Not yet. DraftView currently only supports GitHub. We are building integrations for GitLab and Bitbucket next. Contact us to request priority for your platform.

Question 12

Is my data secure?

Accepted Answer

Yes, all data is encrypted at rest and in transit. We follow industry best practices for security and compliance, including SOC2 readiness. Your documentation, review sessions, and the human-oversight record are protected with enterprise-grade security measures.

Question 13

Is there a free tier or trial available?

Accepted Answer

Yes. DraftView is free forever for individuals and small teams. Reviewing PRs (public or private) is unlimited, and the free plan includes a review queue for 2 repos with 2 active reviewers per month. Connecting your GitHub organization starts a 14-day free trial of the Team plan (unlimited repos and reviewers, no credit card); when it ends you simply drop back to the free plan, and nothing pauses. Team is $29/month per organization with 5 active reviewers included.

How do I review AI-generated documentation before it merges?

Start by catching the pull requests

Review the page, not the diff

Close the loop with the agent

Make sign-off a real step

What to know before you rely on this

Common questions

Keep reading