Review and Publish
Use the Inbox
Find, triage, and assign documentation updates, and understand run states and change types.
Use the Inbox
An Inbox item brings together a documentation run and the work to review: its source context, proposed changes, questions, and activity. One item can cover several pages or articles. A run can also appear before it has changes to review, while it is drafting, waiting for input, or reporting a failure.
Open Inbox from the sidebar to find work across four tabs:
- Open: items that still need attention and are not archived.
- Assigned: items assigned to you, including resolved items that have not been archived. This is not a list of everyone's assignments.
- Resolved: items marked resolved, or items whose review work is finished with no pending changes or unpublished drafts remaining.
- Archived: items set aside from the active queue, whether or not their review is complete.
Admins and Editors can see all workspace items. Contributors see only items assigned to them, in every tab and search result. Assigning an item to someone else removes the previous Contributor's access.
Read the list
Each row has six columns:
- ID: the item's short reference, such as
PL-2BBC. - Title: the request or update the item concerns. Status badges and a pull request icon can give more context beside the title.
- Changes: counts of proposed updates, new pages or articles, and structural changes. While a run needs answers, this column can show the unanswered-question count instead. A failed run can show its failure reason.
- Source: icons identifying the connected service or knowledge base associated with the item. Hover over an icon to read its label; open the item to inspect the source context.
- Priority: High, Medium, or Low, with a reason available on hover. A person can override the derived priority. Rows still drafting, and runs without a review item yet, may have no priority.
- Assignee: the person responsible for the review, or + Assign when no person is assigned. Pageloop can appear here while it is handling the work.
How items reach the Inbox
Items come from documentation runs your team starts and from configured workflows. A run can use a request, an uploaded video, or activity from connected tools, such as merged pull requests, issues, and Slack discussions. Pageloop compares the evidence with your documentation and brings the resulting work into the Inbox. A run can also update an existing item rather than create a separate proposal.
An item appearing in the Inbox does not publish anything. Your team reviews the proposal and an Admin or Editor chooses what to publish.
Triage as an Editor
Admins can follow the same triage workflow. Contributors can open and review their assigned items, but cannot change assignments, delete items, or publish.
- Open Inbox and start in Open, or use Assigned to focus on your own queue.
- Read the row's Priority and hover over the priority to understand its reason. High priority commonly means Pageloop needs an answer before it can continue. Medium can indicate drafted changes, a failed run, or a newer published version that needs review. Low means nothing is blocked on the item.
- Read the Source labels, then click the row's title or ID to open the item. Selecting its checkbox selects the row without opening it.
- Read Activity for the request, source context, questions, and review history. Use Changes to inspect the proposal and Article to read an affected page in context when that tab is available. If Pageloop needs answers, answer its questions before reviewing the resulting changes.
- Assign the item to a Contributor with the right subject knowledge, or keep responsibility for the review yourself. Use the assignee control in the item or the list's Assignee column and choose an active workspace member. Choose your own name to keep the item in your Assigned queue. Choosing No assignee leaves it unassigned; it does not assign the item to you.
Assignment routes the review; it does not publish the changes. A Contributor can review their assigned work and mark it Ready for publish for an Editor or Admin to finish.
Find an item
Use Search events, articles… to search within the selected tab. Search matches item titles and request text as well as affected page or article titles. Contributors' results remain limited to their assignments. Clear the search to return to the tab's full list.
Filter is disabled. Use the four tabs and search to narrow the list.
Select items and use bulk actions
- Select the checkbox beside each item you want to act on. The floating bulk action bar shows the selected count.
- Use the header checkbox, or open the selected-count menu and choose Select all, to select the eligible rows loaded in the list. This does not select every matching item that has not loaded yet. Drafting rows normally cannot be selected.
- Choose a bulk action below. Changing tabs or changing the search clears the selection. To clear it yourself, choose Clear selection in the selected-count menu, use the bar's clear button, or press Escape after closing any open menu.
- Assign — Admins and Editors only. Choose a member to assign all selected review items, or No assignee to clear their assignments. Runs that have not become review items cannot be assigned; including one in your selection disables Assign.
- Archive — Admins, Editors, and Contributors. Contributors can archive only their assigned items. Archive sets work aside without deleting its drafts or review history. In Archived, the action becomes Restore.
- Delete — Admins and Editors only. Delete permanently removes the selected items and their drafts, proposed changes, comments, and activity. It also closes any open pull request associated with the deleted proposal. Deletion requires confirmation and cannot be undone. If an item is linked to an article and cannot be deleted, archive it instead. Wait for an active run or agent update to finish before deleting its work.
The bar also offers Resolve in active views. Admins, Editors, and Contributors can mark visible review items resolved without accepting or rejecting every change; Contributor access remains limited to assigned items. Resolve does not publish anything, and runs without review items cannot be resolved.
If a run fails
Open the failed item and read the failure reason and Details, if shown. An Admin or Editor can use Try again, Run again, or Redo the run when the item offers that action. Follow any instruction to re-record or re-upload the source instead. If no retry is offered on the item, start a run from Home. Contributors should ask an Editor or Admin to restart the run. Review any resulting changes before publishing.
Reference
Run and proposal states
Run progress and publication are separate: Completed means the agent finished, not that your documentation is live. Draft, Published, Merged, and Closed describe the proposal or its delivery rather than the agent's progress.
| State | Meaning | Who needs to act | Next step |
|---|---|---|---|
| Drafting | Pageloop is reading the evidence and preparing or revising changes. | Pageloop; no reviewer action is required yet. | Wait for the run to finish or ask for input. You can leave the page and return through the Inbox. |
| Needs input | Pageloop has paused for an answer rather than guess. The list may say Needs answers or Action required. | An Admin or Editor, or the assigned Contributor when the questions are on their item. | Open the item, answer the questions, and submit the answers so drafting can continue. |
| Draft | A docs-site proposal has not been sent to a pull request yet. This is different from an active drafting run. | The reviewer; an Admin or Editor handles publication. | Review the changes and publish the approved selection when ready. |
| Completed | The run finished; its proposed changes are in the Inbox, or it updated existing items. | The assigned reviewer or an Editor. | Open the changes or follow the links to the items the run updated. Completion alone does not publish them. |
| Failed | The run could not finish. | An Admin or Editor. | Read the reason, address any stated problem, and use the offered retry or start another run. |
| Published | The selected changes were delivered to the connected help center. Delivery can use Live or Draft mode; it does not always mean the articles are public. | An Admin or Editor if further publication is needed in the help center. | Check the delivery result and mode. Publish provider-side drafts in the help center when ready. |
| Merged | The docs proposal's pull request or merge request was merged. | No further review action on this proposal. | Check the resulting documentation after the site's publication or deployment completes. Start another run for further changes. |
| Closed | The proposal was closed without merging or publishing. | An Editor if the update is still needed. | Start another run to create a review; the closed proposal is read-only. |
A run that finds nothing to update can show No changes needed; read its reasoning rather than look for a draft. A run stopped by a person can show Stopped rather than Failed.
Change types
Accepting a change records your review decision and includes the change for publication; it does not immediately change the live documentation. An Admin or Editor must complete the publishing flow. For repository-backed sites, the change reaches the published site through the pull request or merge request and the site's deployment. For help centers, delivery depends on the provider and the selected publish mode. Review any dependency or Draft-mode warnings before confirming publication.
| Change type | What it means | What accepting it does |
|---|---|---|
| Page edit | Proposed content changes to an existing page or article. | Includes the accepted content edits in that page's published result. |
| New page | A proposed page or article that does not exist in the published documentation. | Includes the draft as a new page or article. Review any accompanying sidebar or collection changes separately. |
| Deleted page | Removal of an existing docs-site page. | Includes the page's deletion. Check related sidebar and link changes before publishing. |
| Renamed page | A docs-site page moves from one file path to another. | Includes the path change, which can change the page's public address. Review related navigation and links. |
| Sidebar change | A change to docs-site navigation, such as adding, moving, reordering, or renaming navigation entries. | Includes the proposed navigation change; removing a sidebar entry is not the same as deleting its page. |
| Page settings | A change to a docs-site page's metadata or settings rather than its body. | Includes the proposed settings values. Review body edits separately if the item also contains a Page edit. |
| Image | An image asset addition or replacement used by the proposed documentation. | Includes the image asset with the relevant page changes. A screenshot replacement request may require you to upload a replacement in the editor before it can be accepted. |
| Move (help centers) | An article changes collection, folder, or category membership. | Includes the proposed placement in the help center. The destination depends on the provider. |
| Status (help centers) | An article changes between draft and published status. | Includes the proposed publish or unpublish operation. Check the provider's publishing warnings before confirming. |
| New collection (help centers) | A proposed collection, folder, or category in the help center. | Includes creation of that container. Accept dependent article moves or additions as needed. |
| Rename collection (help centers) | An existing help-center collection, folder, or category gets a different name. | Includes the name change for that container. |

