Customer Access & Organizations for Jira Service Management

Are you having trouble creating a complete list of all your users? Look no further! Our app builds a single list of all users who can raise requests on your restricted service space. This means you will not have to chase down individual accounts for company employees, vendors, and support tickets.

The Customer Access & Organizations app:

Builds a single list of users that shows how each person got access.
Shows what changed since your last review.
Makes organization changes in bulk from a spreadsheet and offers an undo feature.

Try the app for free by joining the beta.

This app is for Jira Service Management Cloud. No sign-up or API token is required. The app installs and works inside Jira. The admins of each service space can use it without requiring Jira admin permission.

After installing the app, open a service space and go to Space settings → Apps → Access report. The guide’s Where to find it lists every page.

What it does

Lists every customer who can raise requests in a service space, and whether they got access through an organization or were added directly.
Shows each person’s account status, how many requests they have raised, and when they last raised one.
Keeps each report as a snapshot, so you can see who gained or lost access since any of the last snapshots. Snapshots can run by themselves each week or month.
Makes organization changes in bulk from a CSV file. Every file is checked first, and nothing changes until you confirm. An applied batch can be undone.
Suggests organizations for people whose email domain matches an organization they are not in yet.
Lists the agents and admins of each space, with the roles and groups their access comes through.
Provides Jira admins one page for the whole site, including Customer Service Management customer experiences.
Adds a dashboard widget with requests, open requests, SLA breaches, and satisfaction for each customer organization.
Exports every list to CSV.

What it looks like

These images are from a demo site with invented companies and people. Select an image to enlarge it, then select it again or press Esc to close it.

The access report's People tab for a demo space shows totals for 655 customers. It also includes a table of each person's name, email, account type, the organization they got access through, and their requests. — The People tab lists everyone who can raise requests in the space, and it also includes how they got access and when they last raised a request.

The Changes tab comparing two reports a week apart shows that 32 people gained access, while 23 lost access. One organization was linked, and one was unlinked. This information is followed by the list of changes. — The Changes tab compares the current report with an earlier one, showing which people gained or lost access and which organizations changed.

A checked bulk file of eight rows shows five rows ready to apply, two rows that need no change, and one error for an unknown action. — In a checked bulk file, each row says what it will do and who it affects, and nothing changes until you apply it.

The Customer access overview for a demo site shows seven service spaces, with totals for those that have a report, need attention, or are open to anyone. A table lists each space's customer access, customers, organizations, agents and admins, report date, and snapshots. — The Customer access overview shows every service space on the site with its report’s totals, on one page for Jira admins.

Documentation and policies

Start with the guide: where to find each page, how access is worked out, and the known limits. How the app handles data says what it reads, changes, and stores, and for how long. The app’s privacy page is part of the Kingston Falls privacy policy, and data processing sets out the data protection terms. For help, see the app’s help page.

Join the beta

The app is in beta, free, with every feature. To join, write to support@kingstonfalls.com with your site’s address. We will send you the beta terms and an install link once you have accepted them.

The beta ends when the app is listed on the Atlassian Marketplace. We will tell you the date at least 30 days ahead, and beta sites will get a discount. Your reports, snapshots, and bulk change records will be kept. A month after the beta ends, the beta version will stop working. To keep using the app, a site admin will need to subscribe.

During the beta, we handle your data exactly as we will for paid use, as the privacy and data handling pages describe. The data processing terms take effect when you subscribe. The beta is provided as is, without warranty, under the beta terms.

Made by Kingston Falls. The app runs entirely on Atlassian’s Forge platform, so your data does not leave Atlassian.