Prerequisites and access
There is nothing to install and nothing to configure. What there is, is a short list of things that need to be true before you start.
The one people miss is the last: the run happens in your browser tab, so the machine it runs on has to stay awake.
#What you need
Requirement | Why |
|---|---|
Confluence administrator, for a site-wide run | The assistant lives in Confluence Settings under Capable |
Space administrator, for a single-space run | The space-level entry point is in space settings |
Read and write access to the pages in scope | The run acts as you. Pages you cannot edit are reported as permission failures |
A backup, or a sandbox | Page history makes a migration reversible; a backup makes it fast |
The Capable app the migrators belong to | Which migrators you see depends on which Capable app you opened |
A browser tab that will stay open | The run happens in your browser tab. Closing the tab stops the run |
Check your power settings before a long run. A laptop that sleeps mid-migration stops the run exactly as if you had closed the tab.
#If you need restricted pages
Restricted pages are skipped and reported as permission failures unless the admin key is active. That has to be switched on in Confluence first, under Settings, Security, Admin key, and it expires on its own timer. See Permissions and the admin key.
#A few things that catch people out
Whoever runs the migration determines its reach. An admin with narrow space access will produce a narrow migration.
You do not need to uninstall the old app first. Keeping it installed is what lets you compare and roll back.
You do not need a licence for the old app to have expired, and an expired one may stop its macros rendering at all.
#Related
One role, one backup, one tab that stays open.
