Version Cleaner for Confluence documentation

Requirements

• Confluence Cloud and access to Version Cleaner from Confluence settings or a space's settings.
• The signed-in person must be allowed to edit each page included in the preview; pages that fail the check are left out.
• An active Marketplace licence is required to start deletion. Preview remains available without an active licence. If the licence becomes inactive, queued deletion work stops before its next batch of pages.

How a cleanup works

• Choose up to 20 spaces, or enter up to 100 page links or identifiers and optionally include descendants. Space runs can also include blog posts.
• Set the latest-version rule, the age rule, or both. The current version is always protected.
• Run the preview. Version Cleaner checks page permissions, counts the affected pages and versions, and lets you download the preview as CSV without deleting anything.
• Review the result, type DELETE and confirm. The job runs in the background, re-reading versions and applying the rule again before each deletion.
• Follow progress, stop the remaining work if needed, and export the audit CSV when the run is complete.

Rules and limits

• Keep-latest accepts 1 to 1,000 versions. Keep-newer-than accepts 0 to 3,650 days. With both enabled, a version must break both rules before it is selected.
• One preview or job can contain at most 5,000 affected pages. A selected page tree can visit at most 5,000 pages, and a page with more than 5,000 versions is skipped.
• Only current pages and blog posts are scanned. Drafts and trashed content are excluded.
• A preview expires after 24 hours. Job and audit records are removed after 90 days.
• Rate limits can delay a job. Version Cleaner retries queued work and stops after 20 rate-limit retries instead of retrying forever.

Permission model

The preview acts as the signed-in person and checks whether that person may update every page that has eligible versions. A failed or unavailable check excludes the page. The queued deletion has no signed-in session, so it deletes as the Forge app. It does not repeat the original person's permission check after confirmation; if that person's access changes between preview and deletion, the approved job can still continue.

Permissions requested

• read:confluence-content.summary and read:confluence-space.summary for the classic content, version and permission endpoints used by the app.
• read:page:confluence and read:space:confluence to list current pages, blog posts and spaces through Confluence's current APIs.
• read:hierarchical-content:confluence to include descendants of selected pages.
• read:confluence-content.permission to check whether the signed-in person may update each affected page.
• write:confluence-content to delete historical page versions after confirmation.
• storage:app for 24-hour previews and 90-day job and audit records.
• report:personal-data to report retained account ids to Atlassian's Personal Data Reporting API and act on closed or updated account responses.

Troubleshooting

• If pages are missing from a preview, check the selected scope and your edit permission on those pages. The preview reports pages excluded by permission checks.
• If a job is delayed, leave it running and check its progress later. Atlassian rate limits can pause queued work.
• If a page fails, export the audit CSV and include the job id and error shown by the app when contacting support. Do not send page content or credentials.