Unitlane Apps
Security and trust
This page is for site admins and security reviewers who check Seatwise before installing it. It covers what Seatwise can do in Jira, what it stores, how long it keeps it, and how to report a security problem. For RequestOps, see the RequestOps security statement.
In short
- Seatwise is built on Atlassian Forge and runs only on Atlassian’s cloud. It has no servers of its own and makes no calls to anything outside Atlassian.
- There is no API key or token to create. Seatwise uses only the permissions you approve when you install it.
- Only Jira admins can open Seatwise. Removing people from groups also needs a site admin, because that is Jira’s rule.
- The daily and monthly checks only read. Every change in Jira happens when an admin clicks, and Jira makes it as that admin, with that admin’s own permissions.
- Seatwise never deletes or deactivates Atlassian accounts.
Permissions
Seatwise asks for 8 permissions. Each one is needed by something it does, and nothing else is requested. Under each permission is Atlassian’s name for it, as your security review may list it.
| Permission | Why Seatwise needs it |
|---|---|
Read Jira usersread:jira-user | To see who is in Jira, which groups they belong to and who has left, and to find a new owner by name. |
Read Jira workread:jira-work | To find when each person last worked in Jira, and to read the spaces, filters, dashboards, permission schemes, space roles, components and plans a person or group is part of. Also to check that the person using Seatwise is a Jira admin. |
Write Jira workwrite:jira-work | To give the filters, dashboards, plans and open work items of someone who left to a new owner, when an admin clicks Hand over. |
Manage Jira projectsmanage:jira-project | To make a new person the space lead or component lead, and to take someone who left out of space roles, when an admin clicks Hand over. Jira also needs it to read work item security schemes. |
Manage Jira configurationmanage:jira-configuration | This one is broad. Seatwise uses it to take people out of the groups that give them a seat when an admin clicks Remove, to add them back on Undo, and to make the new owner the default user of a field that named someone who left. It also reads which groups give product access, who is in each group, notification schemes, work item security levels, workflows and field defaults. Seatwise changes nothing else with it. |
Read Service Management requestsread:servicedesk-request | To list your Jira Service Management service desks, so their queues can be checked for group use. |
Store app datastorage:app | To keep check results, settings, the history of changes and what Undo needs, in the app’s own storage inside Atlassian. |
Report personal datareport:personal-data | To tell Atlassian about once a week which accounts Seatwise stores data about, so that data is erased when someone closes their Atlassian account and updated when their name changes. |
What Seatwise changes in Jira
Only what an admin clicks:
- Remove: takes people out of the groups that give them a Jira seat. Undo adds them back to the same groups, for 30 days.
- Hand over, for people who left: filter, dashboard and plan owners, space and component leads, the default user of user fields, the assignee of their open work items (with Jira’s emails turned off), and their space roles.
Every change is listed in History, with the admin who made it and the result. Seatwise does not delete or deactivate accounts, delete groups, or change permission schemes, notification schemes or workflows.
What Seatwise stores, and where
- Account IDs, display names and avatar links of people on your Jira site.
- Facts about their Jira use: how long since their last Jira work (as a range, for example “no Jira work for 180 days”), which groups give them a seat, and what they own or lead.
- For people who left: the date they left, what they still own, and a suggested new owner.
- Your settings, and the keep list with the reasons you enter.
- If you add Atlassian’s user export: only each person’s account ID, “last seen” date and “added to organization” date. Seatwise reads the file in your browser and never keeps the file itself.
- Cleanup runs and history: who was removed or handed over, by which admin, and the result.
Seatwise does not store email addresses or anything from work items.
Everything is kept in Forge app storage, which Atlassian hosts, and it follows your site’s data residency. Seatwise shares no data with anyone outside Atlassian. Its logs contain no names, account IDs or other personal data.
How long data is kept
| What | How long |
|---|---|
| People with a seat, and people who left | Replaced by each full check, about once a month. The previous copy is deleted. |
| Keep list | Until an admin takes the person off it |
| User-export facts | Until you add a newer export |
| Cleanup previews | The last 5 |
| Cleanup runs | The last 200. Undo works for 30 days. |
| History | The last 300 entries |
| After you uninstall Seatwise | Atlassian keeps the app’s storage for up to 30 days, then deletes it. Seatwise keeps no copy anywhere else. |
Closed accounts and changed names
- About once a week, Seatwise tells Atlassian which accounts it stores, using Atlassian’s personal data reporting.
- When Atlassian says an account was closed, Seatwise erases that person from its lists, the keep list and the user-export facts. In history and cleanup runs, their name and account ID are replaced with “Closed account”.
- When someone’s name changes, Seatwise updates every stored copy.
The privacy policy and the data processing addendum have the full details.
Report a security problem
Email support@unitlane.net with “Security” in the subject. Say which page or screen is affected and how to reproduce the problem, and leave out customer data.
We aim to send a first reply within 1 business day (Monday to Friday, Central European Time), the same as for every other email. Confirmed problems are fixed with an app update, and affected customers and Atlassian are told when an incident needs it.
Who provides Seatwise
Seatwise is made by Jonas Nilsson, trading as Unitlane, a sole trader in Sweden. Support for every Unitlane app goes to the same address.