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

# Finish an Inbox item

# Finish an Inbox item

## Contributors: hand off with Ready for Publish

Use **Ready for Publish** when you have finished reviewing your assigned item and want an Editor or Admin to complete publication. Accepting changes or saving edits does not publish them.

On an assigned item, you can review changes, accept or ignore proposals, edit drafts, answer the item's questions, and comment. You can also archive the item to set it aside without deleting its work. You cannot publish, change assignments, or delete the item. Archiving is not a publishing handoff.

1. From **Home**, open the item with **Review**, or open **Inbox** and find it in **Assigned**.
2. Finish your review and wait for your edits and decisions to save. Resolve any save errors before handing off. If you archived the item, restore it first.
3. Choose **Ready for Publish**.
4. In **Send to**, choose an active Editor or Admin. Add an optional **Note** with anything the publisher should check.
5. Confirm **Ready for Publish**.

Pageloop assigns the item to the recipient and returns you to the Inbox. Because Contributors see only assigned items, you lose access when the handoff changes the assignment.

The recipient receives a ready-for-publish notification and sees the item in their assigned queue. The item's **Activity** records the handoff, and your optional note appears as a comment. Your saved edits and decisions remain for the publisher to check. The handoff does not publish anything.

## Editors and Admins: publish to the Pageloop Knowledge Base

A docs-site item uses a **change set**: a proposal branch and its pull request. Finishing publication means getting that pull request merged into the site's tracked branch and letting the site build complete.

> [!NOTE]
>
> In the Inbox, **Raise PR** submits the proposal; it does not merge it or make the pages live. **Update PR** sends later review changes to an existing pull request. Repository approval rules still apply.

1. Open the reviewed item from **Home**, **Inbox**, or the ready-for-publish notification. Check the Contributor's note in **Activity**, if there is one.
2. Confirm the saved article and review decisions. Check related navigation, images, and page settings as well as body edits.
3. Open **Raise PR**, or **Update PR** if the item already has a pull request. Check the **Publishing to** destination and select the pages and changes to include. Do not assume that every change in the item is selected.
4. Choose the menu's **Raise PR** or **Update PR** action. Read any warning about unsaved edits or undecided changes. Unsaved edits are not included; return to the review if you need them in this publication.
5. Wait for the pull request result, then choose **View on GitHub** or use the pull request link beside the item title. If Pageloop stops because the published article changed, follow the offered review action before submitting again.
6. Have someone with repository access review and merge the pull request. Resolve any required checks, conflicts, or approval requirements in the repository. If you scheduled a merge with **Schedule the merge**, check the scheduled result rather than assuming the time alone guarantees a merge.
7. Wait for the merged documentation to sync and build before checking the live site.

![Inbox Raise PR menu showing the destination and a page that has not been selected](/images/uploads/screenshot-96cd8001.png)

### Confirm the page is live

A **Merged** item confirms the repository merge, not that a site build has completed.

Open **Account** → **Settings** → **Knowledge base**. Check the sync status and the displayed branch and commit against the merged work. When the site is synced, use **View site** and open the affected page. Confirm the expected text, images, links, and navigation on the published site, not only in the Inbox draft or preview.

### If the build fails

1. Open **Settings** → **Knowledge base** and read the reported sync or build error. Distinguish a failed site build from a failure to prepare or submit the pull request.
2. Address the reported problem. If the error concerns repository content or configuration, have someone with repository access correct it and merge the correction. Do not repeatedly raise the same proposal as a substitute for fixing a build error.
3. Use **Sync now** when it is available, then check the status and published page again.
4. If the error does not give you an actionable fix, open **Help and support** from the **Account** menu. Include the item reference, pull request, affected page, and error message so the failure can be investigated.

## Editors and Admins: publish to an external help center

For a connected help center, Pageloop sends the article or accepted operations to the provider instead of merging a docs-site branch. Delivery to the provider and visibility to readers are separate checks.

Use the following flow when the item offers a provider publishing menu, such as Intercom's. Provider controls vary; see the Zendesk notes below rather than assuming the Intercom controls apply to Zendesk.

1. Open the reviewed item and check the final article, decisions, and any handoff note.
2. Open **Publish** and verify the provider shown under **Publishing to**. Select the articles and changes you intend to send.
3. If the menu offers **Live** and **Draft**, choose deliberately. Live mode sends changes for publication; Draft mode saves article drafts for publication in the provider. Read the warnings even in Draft mode: some structural changes take effect immediately.
4. Choose **Publish to Intercom**, or the action naming your connected provider. Review any warning about provider-side edits, unpublished drafts, or dependencies. Return with **Back to review** if the selection needs correction. Use **Publish anyway** only when it is offered and you intend the stated consequences.
5. Wait for the delivery result. A started or in-progress message is not confirmation that every change succeeded. If Pageloop reports only some changes published, read the failed entries on the proposal in **Activity** and follow their instructions.
6. Open the article in the provider. Check its content, images, location, publication state, and audience. Finish any provider-side publication needed, then open the reader-facing article to confirm the result.

### Finish in the provider when needed

- **Draft delivery:** review and publish the saved draft in the help center when you are ready. Pageloop's **Published** state can describe completed delivery; it does not guarantee a public article.
- **Intercom:** check warnings about unpublished drafts before sending changes. Live publication can also publish an existing provider-side draft, and Draft delivery can replace a provider-side draft. Read the stated effect before confirming. If Pageloop reports that someone started a draft during publication, finish or discard that draft in Intercom as instructed.
- **Zendesk:** creating an article sends it as a draft in a section. Review and publish that draft in Zendesk. Updating an existing article's content does not itself change its publication state. Check the article's state and audience rather than assuming a successful transfer made it public. Do not assume Zendesk offers the same Live/Draft menu as Intercom.

If Pageloop cannot confirm that a provider created an article, check the provider before creating another copy. When **Copy article** is offered, use it to create the article by hand only after confirming the article does not already exist; re-add images in the provider because copied image links can expire.

### Help-center change types

Help-center reviews can include content edits and new articles, plus provider-specific operations:

| Change type       | What to check before publishing                                      |
| ----------------- | -------------------------------------------------------------------- |
| Move              | The article's destination collection or folder.                      |
| Status            | Whether the operation publishes or unpublishes the article.          |
| New collection    | The proposed container and any articles that depend on its creation. |
| Rename collection | The container's intended name.                                       |

These operations change provider content and organization, not docs-site files or sidebar configuration. Availability depends on the provider; the Intercom review supports these operations, but they are not a promise that every help center does. Intercom proposals do not delete articles or collections. Ignoring a proposal does not delete provider content.

Decide dependent changes together. For example, an article that belongs in a proposed collection may require the collection's creation to succeed first. Resolve any dependency or provider-conflict warnings before considering the item finished.

## Related

See [The Pageloop sidebar](/guides/pageloop-sidebar) for finding the Inbox, Knowledge Base, and Settings.
