Docs / Bulk Actions for Confluence
Bulk Actions for Confluence documentation
Everything a Jira admin needs to install Bulk Actions for Confluence and everything a user needs to use it.
Install
- Open the Marketplace listing (available at release) and choose Get it now.
- Pick the Jira site to install on. You need to be a site admin.
- Review the permissions below and confirm. Installation takes under a minute.
Permissions
Bulk Actions for Confluence runs on Atlassian Forge and requests these scopes. It does not call any service outside Atlassian.
| Scope | Why the app needs it |
|---|---|
read:page:confluence | List pages and read their current labels and status |
write:page:confluence | Apply status changes and archive selected pages |
read:label:confluence | Show existing labels for filtering and preview |
write:label:confluence | Add or remove labels on selected pages |
read:space:confluence | Browse spaces and page trees for selection |
storage:app | Keep the operation history and results in Forge storage |
Use the app
- Open Bulk Actions from a space and select pages from the page tree, or build a selection with filters such as label, last-updated date, or title.
- Choose an action: add or remove labels, set a page status, or archive.
- Review the mandatory preview, which lists every page and the exact change it will receive. Nothing runs until you confirm.
- Apply. Results show per-page success or failure, and every run is kept in the operation history.
FAQ
Can I undo a bulk operation?
Archived pages can be restored from Confluence's archive, and label changes can be reversed by running the opposite operation on the same selection from the history. Always check the preview first.
Does it respect page permissions?
Yes. The app acts as the user running it and only changes pages that user can already edit. Pages you can't edit are shown as skipped in the preview.
What about changing page owners?
Bulk owner changes are planned for a later release.
Does the app send page content anywhere?
No. It runs on Forge with no external egress; page data stays in Atlassian.
Release notes
Not yet released.