# Getting started

PageCycle gives the pages in a Confluence space a simple workflow: statuses, the moves allowed between them, who may make each move, review dates, automations and a full history. It runs entirely on Atlassian (Runs on Atlassian): PageCycle sends no data to BrainGrid or any outside service.

## 1. Turn it on for a space

You need to be a space admin.

1. Open the space, then **Space settings › Integrations › PageCycle**.
2. Click **Turn on PageCycle**. PageCycle scans the space and lists the Confluence statuses your pages already use.
3. Map each existing status to a PageCycle status (for example "Ready for review" → In review), or leave it unassigned.
4. Click **Turn on**. Pages keep their status; PageCycle records where each one started. Pages you can't edit keep their Confluence status and get no label from you, and PageCycle names them so you can ask someone who can edit them.

PageCycle is off in every space until a space admin turns it on. Turning it off later keeps all history.

## 2. The default workflow

| Status | Kind | Who moves pages in |
|---|---|---|
| Draft | Draft | anyone who can edit (the starting status) |
| In review | In review | anyone who can edit |
| Approved | Signed off | members of `pagecycle-approvers`, with a comment |
| Needs re-review | Needs attention | the "Edited after approval" automation |
| Review due | Needs attention | the "Review date reached" automation |
| Archived | Archived | anyone who can edit |

Create a Confluence group called `pagecycle-approvers` (or pick another group in the workflow editor) and add the people who sign pages off.

## 3. Move a page

Every page in the space shows its PageCycle status under the page title (next to the author), with the next review date when it has one: "Approved · review Mar 12". Click it, pick a move under **Move to**, and confirm. You only see the moves you are allowed to make. Some moves ask for a comment; moves into a signed-off status set the next review date (six months out unless you pick another).

The **History** tab in the same popup lists every change: who, what, when, and why.

## 4. What happens when someone uses the status menu

Confluence can't block a status change, so PageCycle checks each change right after it happens:

- An allowed change is recorded, with the person who made it.
- A change the workflow doesn't allow is put back to the last allowed status, and History says why. A space admin can choose **Flag** instead: the change stays and the page is marked Flagged until an allowed move clears it.

On normal pages this takes a few seconds. Live docs send Confluence no event for status changes, so PageCycle checks them every 5 minutes.

## 5. Next steps

- [Workflows](https://atlassian.braingrid.ai/docs/pagecycle/workflows): add statuses, moves and group rules.
- [Automations](https://atlassian.braingrid.ai/docs/pagecycle/automations): re-review after edits, review dates, labels and comments.
- [Board](https://atlassian.braingrid.ai/docs/pagecycle/board): every page by status, stuck pages, history and CSV.
- [Rovo](https://atlassian.braingrid.ai/docs/pagecycle/rovo): move pages from Rovo chat.
- [FAQ](https://atlassian.braingrid.ai/docs/pagecycle/faq)