Press the one you would buy
Not on sale yet. These tools do not exist yet and may never be built. No payment is taken. Pressing only counts your interest.
Beside this button: what already exists, in its own words
The BulkOps Free listing on the Atlassian Marketplace (ELFAPP Technologies) says:
BulkOps helps in performing bulk operations on Jira cloud, such as deleting Jira users in bulk or bulk creating Jira Service Management organizations.
The BulkOps Pro listing (ELFAPP Technologies) says:
BulkOps Pro helps Jira Cloud admins save hours by automating large-scale user management using simple CSV files. Whether you’re onboarding hundreds of users, cleaning up inactive accounts, or managing JSM organizations.
Read on 9 November 2026: BulkOps Free showed 1,539 installs and 2.607143 stars from 40 reviews; BulkOps Pro showed 224 installs and 3.125 stars from 5 reviews. Prices were not read.
The Atlassian support article “Import customer and organization details through API or CSV” (Jira Service Management Cloud; no update date shown) says:
This will update values into fields that already exist, but it will not add new fields, new customers, or new organizations.
There is a limit of 1,000 rows and a maximum file size of 1MB for each import.
To import more than 1000 rows, you can split the file into multiple files.
The same article opens with:
With the introduction of Service Collection in October 2025, customer service features are no longer available in Jira Service Management on new sites.
The article does not say whether customer and organisation import is among those features, and we did not read how new sites handle customers in Service Collection, so who this would reach on new sites is not known.
Not on sale yet. These tools do not exist yet and may never be built. No payment is taken. Pressing only counts your interest.
Beside this button: what already exists, in its own words
The Atlassian support article “Manage Request Participants with Automation in JSM Cloud” (updated June 29, 2026) has a section headed:
Append/Add multiple Request Participants using the Send web request action
It shows the Send web request action posting a list of account IDs to one work item's participant address, set up per work item. The article says nothing about cost.
On the Atlassian Marketplace, the listing for Bulk Participants for JSM says:
Add, remove, or replace Request Participants across multiple Jira Service Management requests. Preview every change before applying, with permission-aware, fail-safe bulk operations.
The listing showed 1 install and 0 reviews on 9 November 2026. Its price was not read.
Not on sale yet. These tools do not exist yet and may never be built. No payment is taken. Pressing only counts your interest.
Beside this button: what already exists, in its own words
Plainly: the listing for AccessLens (keelapps) on the Atlassian Marketplace describes this job. It says:
Reverse lookup by group, user or space, with group membership expanded to show effective access. Audit page restrictions and what inherits them.
The listing showed 2 installs and 0 reviews on 9 November 2026.
The listing for Warden - Access Audit for Confluence says:
Inventory every view/edit-restricted page across your whole site — direct vs inherited
The listing showed 0 installs and 0 reviews on 9 November 2026.
The listing for Permission Management for Confluence (EB Cloud Engineering) says:
View and manage multiple space permissions and content restrictions for a user or group in a central place.
The listing showed 129 installs and 4.0 stars from 2 reviews on 9 November 2026.
The listing for Space Permissions Overview (Actonic Labs) says:
Thousands of Confluence space permissions at a glance
The listing showed 235 installs and 2.5 stars from 1 review on 9 November 2026. Prices were not read for any of the four.
Bulk import customers and organisations into Jira Service Management from a CSV: the open request
On the public tracker of Atlassian, the request JSDCLOUD-1829, Bulk Import Customers or Organizations from External File
, has 346 votes. It was created on 30 April 2015. Its status is Reviewing
. It was last updated on 9 November 2026 and is unresolved. These figures were read by this page's makers on 9 November 2026.
The Atlassian import article also tells you to start with:
Use the bulk add feature to add new customers to your service project first.
Use the REST API to create new organizations first.
Source: support.atlassian.com/jira-service-management-cloud/docs/import-customer-and-organization-details, read 9 November 2026.
What the sources do and do not support
The built-in Atlassian import is said to update existing records and not to create customers or organisations, and a vendor already lists bulk creation of Jira Service Management organisations. The sources do not show that BulkOps adds customers to organisations, and we did not read what the BulkOps reviews say. They do not show that an outside app can create customers or organisations from a CSV through the Atlassian programming interface: that has not been tested. The offer is one CSV for customers, organisations and who belongs to which. The 1,000-row limit applies to the built-in Atlassian CSV import, not to any tool described here.
Bulk change request participants in Jira Service Management: the open request
On the public tracker of Atlassian, the request JSDCLOUD-1269, Allow to bulk change "Request participants"
, has 262 votes. It was created on 14 December 2014. Its status is Future Consideration
. It was last updated on 7 November 2026 and is unresolved. These figures were read by this page's makers on 9 November 2026.
The same support article says:
You can't write email addresses directly into Request Participants — it's a user-picker field that requires account IDs.
Source: support.atlassian.com/jira/kb/add-update-remove-request-participants-using-automation-in-jsm-cloud, read 9 November 2026.
What the sources do and do not support
A route through Atlassian Automation is documented, and one listed app already offers add, remove and replace with a preview. The sources do not show how many requests the Automation route can change in one run (the article gives no limit and we did not test it), do not show the listed app's price, and do not show that admins would pay for a hosted alternative. Other apps may exist: we read only the one listed here.
Confluence report of the spaces and restricted pages a group can access: the open request
On the public tracker of Atlassian, the request CONFCLOUD-74405, List which spaces and (restricted) pages a group can access
, has 125 votes. It was created on 12 August 2022. Its status is Gathering Interest
. It was last updated on 8 November 2026 and is unresolved. These figures were read by this page's makers on 9 November 2026.
The Atlassian support article “Inspect a user's permissions” (Confluence Cloud; no update date shown) says:
This feature is offered with Confluence Cloud Premium.
The article says you can inspect a user's permissions from the content itself, for view, view and edit, and view and comment. Source: support.atlassian.com/confluence-cloud/docs/inspect-a-users-permissions, read 9 November 2026.
What the sources do and do not support
The job this button describes is already described in the listing words of AccessLens, which has no reviews. Warden's listing words describe a site-wide inventory of restricted pages. Permission Management's listing words cover content restrictions for a user or group across spaces. The sources do not show whether any of these covers every space and every restricted page for a group, do not show their prices, and do not show whether the Confluence programming interface can produce such a report quickly on a large site: that has not been tested.
What one press counts
This page is a test of interest, not a shop. There is no payment form, no email field and no free-text box anywhere on it. The GBP 15 once, GBP 3 a month and GBP 4 a month figures are guesses and have not been tested with any buyer. Pressing a button records one anonymous count for the day for that button only, and a short tag if the link you followed carried one. A press on one button is never counted as interest in another. No cookie is set and no address is kept. One press is allowed per button per page load.