.png)
Admin guide
The app has no settings of its own. This is what an administrator controls around it.
The app acts as you, never as itself
Every read, move and rename is made with your Confluence account: in the browser while you arrange pages, and in the app’s backend while a save runs, acting for the person whose tab started it. The app has no service account, no elevated identity and no way to act for someone who is not using it — if Confluence would refuse you, it refuses the app.
That is why there is nothing to configure. Your existing Confluence permissions already describe exactly what the app can do, and it never does more than you could do by hand. Two people opening the same parent can see different pages and be allowed different things.
Space permissions
Seeing a space’s page tree and changing it need different permissions.
| To | What you need | Without it |
|---|---|---|
| See a space and its pages | Permission to view the space | The space is not listed under Choose a space to organize or in Move to…, and its pages never appear. |
| Change the order, or move pages out of a space | Space admin, or Manage all content on sites that use space roles — what Confluence’s own Move needs | You see the order but can’t select, drag, sort or save, and a banner says why. |
| Move pages into another space | Whatever Confluence asks of you there, checked as each page moves | Those moves are refused at save and named in the result. Everything else in the save still goes ahead. |
The banner reads You can see this order but not change it. Moving pages needs Space admin or Manage all content in Team Handbook. Confluence has no single “move” permission an app can ask about, so the app checks for those two space permissions when the organizer opens — the pair Confluence’s own Move relies on.
Page restrictions
Page restrictions apply exactly as they do everywhere else in Confluence.
- A page you can’t view never appears — not in the list, not in the page tree, not in Move to…. The app can’t select it, sort it or reveal its title.
- A page you can view but Confluence won’t let you move is tried at save, refused, and left where it is. The pages around it still move, and the result names it: 6 pages moved. 2 pages couldn’t be moved: “Travel”, “Security”. They may be restricted, or you may not have permission.
One refused page never stops the rest of a save. Each page is moved on its own, so a save does everything you are allowed to do and lists what it couldn’t.
Rules no permission lifts
Some refusals come from Confluence itself and apply to everyone, site admins included. The app checks for them before a move is staged, so nobody finds out only when saving.
- More than 1,000 items beneath a page. Confluence won’t move a page like that at all, not even with its own Move, so it can’t go into another page or space. The app marks it Too big to move out. It can still be dragged up or down among its siblings: the pages around it move instead. Two pages like that can’t swap places, so they keep their current order and everything else is arranged around them.
- Titles are unique within a space, ignoring case. Moving a page into a space that already has its title is refused, so the app asks first: Rename and move, to a free title such as “Travel (1)” like the one Confluence’s own Move suggests, or Leave it out.
- A page can’t go inside one of its own child pages. That move is left out, and the panel beside the list says why.
Every limit, and what happens at each, is on the Limits page.
Installation and access
Page Order is an Atlassian Forge app. It installs site-wide and needs a Confluence site administrator, because Forge apps cannot be installed per space. Once installed it is available to everyone, and what each person can change is decided by their own space permissions, above. There is no settings screen and no admin page.
It requests seven scopes, and nothing else:
- write:confluence-content — to move pages, with Confluence’s move API
- write:page:confluence — to rename a page whose title is already used in the space it is moving to
- read:hierarchical-content:confluence — to read a parent’s child pages in page tree order
- read:page:confluence — to read pages’ titles, parents and dates
- read:folder:confluence — to read folders’ titles, parents and dates
- read:space:confluence — to list spaces, and check whether you can move pages in one
- search:confluence — to find a page by title in Move to…, count what is beneath a page, and show when each space was last updated
It has no app storage, no database, no triggers and no background jobs, and it sends nothing outside Atlassian — it carries the Runs on Atlassian badge, so there is no external server to allow-list. A save runs only while the tab that started it stays open. Uninstalling from Apps → Manage apps leaves nothing behind, because nothing was stored; pages stay where the last save put them.
The step-by-step install is under Get started → Installation.
Licensing
Page Order is free for teams of 10 users or fewer, and billed per user through the Atlassian Marketplace above that, on your existing Atlassian invoice. Billing is Atlassian’s — the app never sees a payment detail, and there is nothing to set up inside it.
The licence is checked every time the app opens. If the site’s subscription is not active — a trial that ended, or a subscription that lapsed — every way in shows Page Order needs an active subscription on this site. Ask your Confluence admin to start a trial or subscribe from Manage apps. and nothing can be sorted or moved. Pages already saved are unaffected: their order is Confluence’s own.