For the page tree where new pages land at the bottom
Sort a page tree once, and the next new page still lands at the bottom.
Confluence can sort a page's children A to Z once, from Space settings → Reorder. Add a page tomorrow and it goes to the bottom again. Sort Pages keeps a rule instead: set it on a page, a folder or a whole space, and pages that are created, renamed, moved or restored fall into place within a minute — A to Z with natural numbers, Z to A, newest first or oldest first. Only the order changes. Nothing leaves Atlassian.
Zero egress. Reordering creates no page versions and sends no notifications.
- Works in
- Confluence Cloud
- Runs on
- Atlassian Forge
- Your data
- Never sent to us
- Status
- Coming soon
The gap this fills
CONFCLOUD-65454 — keep pages permanently sorted alphabetically — has 625 votes and sits at Under Consideration; in April 2025 the product manager wrote that it is harder than it looks, and nothing has moved since. Its neighbours ask for a reverse sort (CONFCLOUD-31358) and for reordering as pages are created or updated (CONFCLOUD-77875), and Atlassian's own bug report CONFCLOUD-82423 notes that the built-in A to Z sort can fail without an error when the person sorting cannot edit every page.
So spaces drift. Someone sorts the tree by hand, a colleague adds a page, and it lands at the bottom. Two months later nobody can find the runbook, and the meeting notes are in the order they happened to be created.
Capabilities
What it does
Rules that stick
Set a rule once on a page, a folder or a whole space. Pages created, renamed, moved, copied or restored fall into place within a minute, and a weekly check catches anything that slipped through.
The order people expect
A to Z with natural numbers: Chapter 2 before Chapter 10, 1.9 before 1.10, dates in date order. Case and accents never split a list, and the result is the same every time.
Newest first, for meeting notes
Newest or oldest by creation date, so this week's notes sit at the top however many are added — or Z to A, if that is what your team means by sorted.
Exceptions, and pins
The nearest rule wins, so a sorted space can keep its release notes newest first and its onboarding section exactly as arranged. Pin Overview to the top and Archive to the bottom.
Undo to the original order
Before its first move, Sort Pages records the order it found. One click puts every list back the way it was and pauses the rule.
Fewest moves, no noise
Each sort moves as few pages as possible — one new page costs one move — creates no page versions and sends no notifications. Restricted pages stay put and the rest are sorted around them.
Walkthrough
From one messy list to a space that stays sorted
-
Preview one page's children
On any page, ••• → Apps → Sort child pages. Pick an order and read the preview: every child in its new position, marked moves or in place. Nothing has changed yet.
-
Keep them sorted
Keep sorted saves a rule on the page — for the pages directly under it, or every level below. From then on a new page falls into place about twenty seconds after it is published.
-
Sort the whole space, with exceptions
In space settings, a space administrator adds a whole-space rule, then exceptions where a section should be ordered differently or left alone. The nearest rule always wins.
-
Change your mind
Restore the earlier order and every list the rule touched goes back the way it was, with pages created since placed at the end. The rule pauses, so nothing re-sorts it.
Compared honestly
Against what Confluence does today
| Question | Native Confluence | Sort Pages |
|---|---|---|
| Stay sorted after someone adds a page? | No — the A to Z sort is one-off | Yes, within a minute |
| Z to A, or newest first? | A to Z only | A to Z, Z to A, newest or oldest first |
| Every level of a space at once? | One list at a time | Whole space, with exceptions |
| A page that cannot be moved? | The sort can fail without an error (CONFCLOUD-82423) | It stays put, the rest are sorted around it, and the log says so |
| Back to how it was? | Undo Sorting, on the Reorder page | Restore the order from before the first sort, at any time |
Limits
Limits we state up front
Within a minute, not instantly. Confluence tells the app about a change a second or two after it happens; the app then waits about twenty seconds so an import or a page and its first edits become one sort rather than dozens.
The top level of a space is not sorted. Confluence warns that positioning a page against a top-level page can take it out of the page tree. A whole-space rule covers everything under the home page — which, in a normal space, is everything.
Pages the app may not move stay where they are. A page restricted so that the app cannot see or edit it keeps its position; the rest of the list is sorted around it, and the activity log says so rather than pretending the list is in order.
Very long lists are refused, not half sorted. A single list of more than 2,000 items is reported as too large.
No “recently updated first”. Deliberately: it would rearrange the page tree every time anyone saved an edit.
Availability
Coming to the Atlassian Marketplace.
Sort Pages for Confluence is built and deployed on Atlassian Forge and is being prepared for Atlassian Marketplace review. This page will link to the listing as soon as it is live.
Licensing is handled by Atlassian. Sites with 10 users or fewer pay nothing at all; paid tiers are priced per user and taper as the site grows.


