Know who checked each page, and until when.

Mark a page verified for 7, 30 or 90 days, or until a date you pick. Add approvals before anything goes live. Every change keeps the name of the person, or the agent, who made it.

A page can be published and still be wrong.

Most docs tools tell you when a page changed. Few tell you when someone last confirmed it was right. Without that, every page looks equally trustworthy, and the stale ones hide among the rest.

Trust you can see, page by page.

  • A verified mark

    Says who verified the page and until when, in the editor and in the Documents list.

  • An end date

    Verify for 7, 30 or 90 days, until a date, or with no end. When it lapses, the page shows as Expired and the people on it are told.

  • Outdated on purpose

    Mark a page outdated by hand. Or link a Linear or Jira issue, and the page is marked outdated when the issue is done.

  • Approvals

    Ask people by name or by email to approve a page before it can publish.

An approval belongs to the words that were approved.

Set up a workflow with your own statuses, and add approval and checklist gates before a page can publish. An approval is tied to the exact text. If someone edits the page afterward, the approval resets, and you can see what changed, sentence by sentence, or restore the approved version.

  • Publish anyway needs a reason, is recorded and is emailed to the approvers.
  • An API token can never override a gate.
  • With no workflow set up, nothing is gated.

Questions

Anyone with editor access to the page. Everyone who can open it sees who verified it and until when.

Know which pages you can trust.

Import them from their address, connect GitHub, and review the first suggested updates in your own workspace.