After you merge code, SupportPages turns those changes into draft content for your help centre and announcements. The **Inbox** is where all of that work waits for you — one place to see what needs a look before anything goes live.

## Prerequisites

- A connected repository with at least one merged pull request or analyzed commit

## Key concepts

### Step 1: Your review queue after a merge

When a pull request merges, SupportPages reads the diff and writes a changelog-style summary of what changed. That analysis can queue new **Suggestions**, start drafting **Articles**, or create **Feature Posts** — depending on what the change means for your users. You do not need to watch Code History for this; new work shows up in the **Inbox** automatically.

### Step 2: One screen, three sections

Open **Inbox** from the left sidebar to see everything pending. The page title reads **Inbox**, with the subtitle **Review suggestions and articles for your Help Centre.** The list on the left is split into up to three groups — **Articles**, **Feature Posts**, and **Suggestions** — and the panel on the right is where you read and act on whichever item you select.

### Step 3: Articles — draft help-centre guides

**Articles** are full how-to or reference guides SupportPages drafted from your recent changes. Each row shows the article title and its help-centre section. When generation finishes, you can review the prose, approve it to publish, or reject it. While a draft is still generating, you will see a spinner on that row instead of the ready-for-review icon.

![Articles — draft help-centre guides](https://help.supportpages.io/rails/active_storage/blobs/proxy/eyJfcmFpbHMiOnsiZGF0YSI6NDU2NywicHVyIjoiYmxvYl9pZCJ9fQ==--894794f3ca35df774a786931911e6b0944235a32/step_2.png)

### Step 4: Feature Posts — launch copy for social channels

**Feature Posts** are short announcement drafts — a title, hook, body, and hashtags — meant for sharing a shipped feature. They sit in their own **Feature Posts** group below articles when that feature is turned on for your project. Like articles, each post waits in the **Inbox** until you approve or reject it.

### Step 5: Suggestions — topics you can accept or skip

**Suggestions** are article or social-post ideas SupportPages spotted in a merge but has not written yet. Each suggestion shows a title and, for article ideas, the target section. Click one to read the description and why it was recommended — many link back to the source pull request. **Accept** to start generation, or **Reject** to dismiss the idea.

### Step 6: When the Inbox is empty

If nothing is waiting, you will see **All done!** with **No pending items to review.** in the list and a confirmation in the right panel that you have reviewed everything. The badge on **Inbox** in the sidebar clears too. New items appear the next time a merge triggers analysis — check back after your next release.

## Tips

- The pending count next to the page title adds up unreviewed suggestions, articles, and feature posts so you can see at a glance how much is left.
- Use **Generate all** on the **Suggestions** header to accept every topic at once when you trust the batch.

## Summary

The **Inbox** collects everything SupportPages produces from merged code — draft **Articles**, **Feature Posts**, and **Suggestions** — in one review queue. Open **Inbox** after each release to work through the list and publish what your users need.