Pagecycle
A workflow for
Confluence pages
Your own statuses, the moves allowed between them, review dates that remind owners, and a history of who moved each page and why.
Free 30-day trial
Built for humans and agents
Everything people do in Pagecycle, an agent can do too: check a page, move it, set its next review, find what's overdue, or change a space's workflow. In Rovo, or from Claude, Codex and Cursor over MCP, with exactly its user's permissions.
What Confluence does, and what Pagecycle adds
Pagecycle builds on Confluence's status instead of replacing it, so every improvement Atlassian ships still works.
| Confluence today | With Pagecycle | |
|---|---|---|
| Who may move a page, and where | Anyone who can edit sets any status | Allowed moves, group rules and required comments |
| Sign-off on the Standard plan | Approvals are Premium and Enterprise only | A sign-off move limited to a group, on every plan |
| Review-by dates | Not available | Pages move to Review due and the owner is mentioned |
| Edited after sign-off | Nothing changes | The page goes back to Needs re-review on its own |
| Every page by status | No board of pages by status | A board per space and across spaces, with CSV |
| Status history you can export | Page versions only | Every move with person, time and comment |
Rules for every move
- Your own statuses and the moves between them
- Each move says who may make it
- Approvers sign off with a comment that says why
- Confluence's status menu keeps working
- A move your workflow doesn't allow is put back and recorded
Pages that move on their own
Two automations ship switched on, and space admins build more from When, If and Then. Each runs once per occurrence, and History names it on every change it makes.
Who, when and why
- Who moved the page: a person, an automation or an agent
- When, and the status before and after
- The comment they left
- Kept as long as you choose, and downloadable as CSV
- Page content and titles are never stored
Checked the 10,000-row limit with engineering. Ready to build.
Added XLSX export from the customer interviews.
Your pages never leave Atlassian
Pagecycle runs on Atlassian: no remote back end, no external services.
Pagecycle- Page content and titles are never stored; edits are noticed by a fingerprint of the page body
- The board counts a page only after checking the viewer's permission on it
- Uninstalling deletes Pagecycle's stored data; page statuses stay on your pages
Questions admins ask
How do we roll it out?+
Turn it on in one space, set its statuses and the moves allowed between them, and add spaces as teams are ready. Each space can run its own workflow.
What do people see on a page?+
The page's status under its title, its next review date, and a Move to button that offers only the allowed moves. History shows who moved the page, when and why.
Does it work with Confluence approvals?+
Yes. On Premium and Enterprise, Pagecycle respects every approval: it checks Confluence before each automatic move and asks before a move would end an approval.
Where is our data?+
In your Confluence site. Workflows and history live in Atlassian's storage and follow your site's data residency. Nothing is sent outside Atlassian.
What if we change our minds?+
Statuses stay on your pages, because they're Confluence's own. Uninstalling removes Pagecycle's stored workflows and history.
Put your next
spec on Pagecycle
Install from the Atlassian Marketplace and turn it on in one space.