Source: https://docs.pageloop.ai/guides/review-inbox-item

# Review an Inbox item

# Review an Inbox item

An Inbox item brings together Pageloop’s proposed documentation changes and the conversation about them. Review each change against its sources, check the draft in context, and decide what to keep before publishing.

> [!NOTE]
>
> Admins and Editors can review items and use Ask. Contributors review items assigned to them and hand finished work back with **Ready for Publish**; Contributors cannot publish or use Ask.

## Open the item and choose a view

1. Select **Inbox** in the sidebar and open the item you want to review. Use **Assigned** to find items assigned to you.
2. Start with **All changes** in the left-hand navigation to see the proposal together, or select a page to focus on its changes.
3. Switch between the item’s tabs as you review:

| Tab          | Use it to                                                                                                                                                                   |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Changes**  | Compare individual proposals and accept or dismiss changes.                                                                                                                 |
| **Article**  | Read a selected page with its changes in context and edit the draft. Select a page on the left first; navigation and other non-article changes do not have an Article view. |
| **Activity** | Read the item’s summary, review history, question rounds, and comment threads. Activity covers the whole item, not just the selected page.                                  |

If Pageloop is waiting for answers, the item can open on **Activity** instead of a draft. [Answer the question round](#answer-a-question-round) before reviewing the resulting changes.

## Read a change card

In **Changes**, expand a card with its chevron. Read the card in this order:

1. **Headline and type.** The headline describes the proposed edit. The badge identifies an addition, update, move, or deletion; a proposed page can show **New**.
2. **Before and after.** Green highlights mark additions; red highlights mark removals. A replacement contains both. Structural changes, such as page settings or navigation, can show **Old** and **New** comparisons instead of a text edit.
3. **Reason and evidence.** Use the sparkle beside the headline to open **Why Pageloop suggests this**, when available. Follow linked sources to check the evidence behind the change.
4. **Surrounding article.** Select **View In Article →** to read the proposal beside the rest of the page. Check that the edit fits the instructions, terminology, and intended audience.

Do not approve a proposal solely because its explanation sounds plausible. Check the source and the resulting article, especially for permissions, limits, and workflow steps.

### Accept or dismiss changes

- Select **Accept** to keep a proposed change.
- To dismiss a change in **Changes**, select the X control, labeled **Ignore**. The card then shows **Ignored**. Dismissing leaves that proposal out of the accepted result; it does not delete the published article.
- Use **Undo** on a decided card to return the change to pending while the proposal is still editable.
- To accept the item’s pending changes together, open **More actions** on **Changes**, select **Accept all**, and review the confirmation before proceeding. Check the full item first: this action is not limited to the page selected on the left.

The Article tab also has page-level review controls. **Accept All** there applies to the selected page, not the whole item. Read any warning or disabled-control explanation before continuing; a change that needs a manual image replacement or a separate conflict decision may not be ready to accept.

### Edit the draft

1. Select the page in the left-hand navigation and open **Article**.
2. Edit the draft’s text directly. For documentation pages, use **Page** for the rendered editor or **MDX** to work with the source.
3. Open a highlighted change’s margin card to read its explanation and review controls. Use **Show More** if the explanation is shortened.
4. Wait for edits and decisions to save before leaving the item or publishing. Resolve any save conflict shown by the editor rather than assuming the edit was saved.
5. Use **Final article** to check the page with accepted changes included and unaccepted proposals left out, without review markings. Return to the review view to continue editing. A proposed new page is already its own draft and does not need this toggle.

For stale or missing images, follow [Get correct images into drafts](/guides/correct-images-in-drafts) for retaking screenshots and capturing replacements.

### Inspect reasoning and reviewed sources

Use the card’s **Why Pageloop suggests this** explanation and source links for an individual edit. In **Article**, the margin card also shows the explanation and a **Sources** row when evidence is available. In **Activity**, read the proposal’s summary for the reasoning behind the item as a whole.

A run that finds nothing to change can show **No changes needed** and **Nothing to update** rather than change cards. Read that summary, expand **Full reasoning** when offered, and inspect **Reviewed sources** for the records Pageloop checked and why they did not lead to edits. Source links open the original records when a link is available. A no-change result is different from dismissing a proposal yourself.

### After every change is decided

When no changes remain pending, review is complete, but your decisions do not publish the documentation. Accepted changes form the reviewed result; ignored changes stay out. **Activity** records the decisions, and editable decided cards retain **Undo**.

Deciding every card does not necessarily move the item out of **Open**. An open documentation proposal keeps the item there until you finish the publishing or change-request process. The item resolves automatically once its proposal is no longer open, no changes remain pending, and any new article drafts have been published or dismissed. Find the finished item under **Resolved**. **Archived** is a separate place for items you deliberately archive; completing review does not archive an item.

If you are a Contributor, select **Ready for Publish** to hand the reviewed work back to a teammate who can publish.

## Answer a question round

Pageloop pauses when an answer is needed to decide a specific edit, such as who can use a feature or whether a change has shipped. The item needs input rather than more review: it can show **Needs input** or **Needs answers**, with a question count. The agent waits instead of guessing at the decision.

### Find and answer the questions

1. Open the item’s **Activity** tab and find **Pageloop asked you …**. The question-round card shows the next question and where to answer it.
2. Select the card to open the item’s Ask sidebar. If your role does not have Ask, follow **Answer in the Changes tab** instead.
3. Read the question and its **Decides** line. The line explains which documentation edit your answer controls.
4. Choose an option, or use **Or type your own answer** when offered and select **Send** to save the typed answer. You can add details before selecting an option. For a question that allows multiple choices, select the applicable options and choose **Use selected options**.
5. Continue through the round. To revise an answer before submission, select it under **Your answers**.
6. Read the recap of what Pageloop will do, then submit the round. The Inbox control is **Suggest the changes**; the Ask sidebar can show **Send answers**.

Selecting answers saves the choices, but the final submission starts the continuation. Pageloop resumes the run using those answers and shows progress while it works. When the run finishes, use **Open the changes** if offered, or follow links to existing items the run updated. Review the resulting draft; answering questions does not accept or publish changes. Pageloop can also conclude that nothing needs to change after reading your answers.

**Activity** records the submitted answers and the resumed run, so reviewers can see which decisions shaped the proposal. Change cards can also identify the answers behind an edit.

### Give answers the agent can use

- Answer the decision in the **Decides** line, not just the general topic.
- Name the affected page, feature, role, or plan explicitly. For example: “Document this for Admins only; Editors can view the result but cannot change the setting.”
- For rollout questions, distinguish shipped behavior from a plan or limited rollout. Give the release scope and supporting source when you have one.
- Include exact labels and the replacement wording when wording matters. For example: “Use ‘Workspace’ throughout this procedure; the menu no longer says ‘Team’.”
- State what should stay unchanged. For example: “Update the setup steps, but keep the existing troubleshooting section.”
- If you cannot confirm a fact, say so rather than guessing. Explain a safe fallback, such as leaving the existing instructions unchanged.

### If a question is left unanswered

Leaving the item or stopping partway through the round does not resume the run. The round remains open until you submit it.

After answering at least one question, you can choose **Let the agent decide the rest** when available. This explicitly submits the answered questions and leaves the others to the agent’s defaults. The round identifies the questions left to the agent, and Activity records the partial submission. Use this only when you are comfortable letting Pageloop choose the remaining edits; it is not the same as providing a confirmed fact.

A typed answer that does not settle the question can still leave the underlying fact unconfirmed. Make the intended edit explicit, or tell Pageloop to leave that part unchanged, then check the resulting proposal.

## Collaborate in comments

### Leave a comment or mention a teammate

1. For feedback on one change, expand its card and use **Leave a comment…**. For feedback on the whole item, use the composer at the bottom of **Activity**.
2. Type your feedback. To involve a teammate, type `@`, start typing the teammate’s name, and select the person from the mention list. For example: “@Alex, can you confirm which roles can export reports?”
3. Select **Send comment**. In a plain paragraph, you can also press Enter to send; use Shift+Enter for a line break.

A teammate mention notifies the selected person. The comment appears in **Activity**; comments anchored to a change also appear with that change. Use the thread’s reply control to keep the discussion together. A comment alone does not accept or dismiss a proposal.

### Ask Pageloop for a change or an answer

> [!NOTE]
>
> Admins and Editors can ask the agent through `@Pageloop` comments. Contributors can leave review comments, but must ask an Admin or Editor to mention Pageloop for agent help.

Type `@Pageloop` in a comment and describe the change or question. Use a change-card comment for a request about that edit, or name the page and section explicitly in an item-wide comment.

Examples:

- “@Pageloop, shorten this explanation to two sentences and keep the warning about Admin access.”
- “@Pageloop, update the Export reports section to say that only Admins can create exports. Leave the download steps unchanged.”
- “@Pageloop, which source supports the seven-day retention limit in this change?”
- “@Pageloop, explain why you updated this page instead of creating a separate article.”

The mention sends the request to your own Ask conversation for this item. Pageloop posts a short reply in the same comment thread in **Activity**, where teammates can read it. As the person who mentioned Pageloop, you also see **Open the chat** for the full conversation; teammates do not gain access to your chat. If the request is attached to a change, the reply keeps that context. If Pageloop needs clarification, open your chat to answer the follow-up question.

Read the reply and inspect the draft again after an edit request. A posted comment is not proof that the requested change has been made. Review and publish any resulting changes separately.
