Get Started

How Pageloop works

How Pageloop detects product changes, drafts updates, and brings them to your team to review and publish.

How Pageloop works

Your product keeps shipping, but your documentation can fall behind. A workflow changes, a setting moves, or a screenshot stops matching the screen customers see—and someone has to find every affected page and fix it.

Pageloop helps teams that maintain a docs site or help center keep their documentation aligned with their product. It watches for product changes, drafts updates with text and screenshots, and brings the work into one Inbox for your team to review and publish. The agent researches and drafts; your team decides what reaches customers. Pageloop never publishes on its own.

The documentation loop

1. Detect a change

An Admin connects your knowledge base and source tools in Integrations. An Editor or Admin configures Workflows to check merged pull requests or Jira, Linear, and Slack activity for changes that matter to readers. Connecting a source alone does not start every kind of check: the source scope and workflow determine what the agent watches.

You can also request work directly. An Editor or Admin can upload a video with a documentation request or describe a change in Ask, giving the agent evidence without waiting for a scheduled check. See Where Inbox items come from for the sources and setup involved.

2. Draft the update

The agent reads the evidence, searches your existing documentation, and drafts changes to the pages that cover the topic. It can prepare text and screenshots, using your connected product and configured screenshot access where available. An Admin can set up automated screenshots so the agent can reach the app screens you want documented.

The proposal appears in the Inbox with its supporting sources. If the agent needs a decision before it can finish, it asks a question rather than guessing; an Editor or Admin, or a Contributor assigned to that item, supplies the answer.

3. Review it in the Inbox

An Editor opens the item, checks the proposed text and screenshots against the sources, and accepts, dismisses, or edits the changes. The Editor can assign the item to a Contributor with the right subject knowledge; Contributors can review only items assigned to them.

The Contributor checks the draft and uses Ready for Publish to hand it back to an Editor or Admin. Accepting changes and handing an item back do not publish anything. See Review an Inbox item for the review screens and controls.

4. Publish it

An Editor or Admin checks the reviewed result and authorizes publication through the Inbox item's publishing controls. Contributors cannot publish, and the agent does not decide to make a draft live.

For a repository-backed docs site, submitting the proposal opens or updates a pull request; the changes reach readers after the pull request is merged and the site builds. For a connected help center, the publisher checks the delivery mode and completes any publication required in the provider. Follow Finish an Inbox item to publish and confirm the result.

Example: a merged pull request becomes an updated guide

Suppose a merged pull request changes how customers configure notifications. A configured workflow starts the agent, which finds the notifications guide and proposes revised steps with a screenshot of the changed settings. An Editor opens the proposal in the Inbox and assigns a Contributor to check the instructions. The Contributor makes corrections and hands the item back with Ready for Publish; the Editor checks the result, submits the docs pull request, and has it reviewed and merged before confirming the updated page on the live site.

Start with your role

Read the articles for your work in the order listed below. Admin, Editor, and Contributor are workspace roles; Developer describes an audience, not a separate permission role.

Admin

As an Admin, you manage workspace settings, members, and roles, and you are responsible for connecting and configuring workspace integrations. You give the agent access to the knowledge base and sources your team needs, and you can also review and publish documentation.

  1. Set up your workspace
  2. Connect your knowledge base
  3. Manage members
  4. Where Inbox items come from

Editor

As an Editor, you start documentation work, review and revise proposals in the Inbox, and assign items to Contributors when you need their expertise. You publish the reviewed result, while an Admin handles integration setup.

  1. Use the Inbox
  2. Review an Inbox item
  3. Finish an Inbox item
  4. Write an article

Contributor

As a Contributor, you review and edit only the Inbox items assigned to you, checking the proposed text and screenshots for accuracy. You hand finished work to an Editor or Admin with Ready for Publish, rather than publishing it yourself.

  1. Use the Inbox
  2. Review an Inbox item
  3. Finish an Inbox item

Developer

As a developer, you work with an Admin to connect repositories—only an Admin can configure workspace integrations—and use pull request checks to catch documentation problems in repository review. You also connect AI agents over MCP (Model Context Protocol), with access limited by your Pageloop workspace role and the permissions you grant the connection.

  1. Connect your knowledge base
  2. Check documentation pull requests
  3. MCP tools and prompts