How it works

Which versions are deleted. For each page and each attachment, Pruner keeps the newest versions you asked for. Of the older ones, it deletes those older than your minimum age (or all of them if the minimum age is 0). The current version and the page content are never changed.

Renumbering. Confluence renumbers the remaining versions after a deletion. If a page had versions 1 to 30 and you keep 10, the remaining versions are numbered 1 to 10 afterwards. The content of each remaining version is unchanged.

Preview and clean-up by an admin. These run with the permissions of the admin who starts them, so they also cover restricted pages that admin can see. Pages the admin cannot see are skipped.

Nightly clean-up. Runs as the app, once a day, with the saved policy. Pages restricted to named people are not visible to apps and are skipped; run a manual clean-up as an admin to include them.

Storage figures. The preview adds up the size of the attachment versions that would be deleted. Page text versions are small and are counted, not sized.

Limits. - Deleted versions cannot be restored. Always preview first. - Large sites are processed in steps. Keep the Pruner page open during a manual clean-up; the nightly clean-up continues in the background until it is done. - Pruner deletes versions of pages and their attachments. Blog posts, comments and whole pages are not changed.

What Pruner stores. Its settings (the policy and the chosen space keys) and a summary of the last run, including the titles of up to 10 pages with the most old versions. Everything stays in Atlassian’s Forge storage; Pruner makes no calls outside Atlassian.