Permissions and limits

Permissions and privacy

Seatwise is built on Atlassian Forge. It needs no API key, and your data stays in Atlassian. Here is each permission and why it is needed.

ForJira admins, site admins and security reviewers

  • Seatwise makes no calls to servers outside Atlassian. The user export is read in your browser, never uploaded as a file.
  • Only Jira admins can open Seatwise. Removing people from groups also needs a site admin, because that is Jira's rule.
  • Daily and monthly checks only read. Changes happen only when an admin clicks, and Jira makes them as that admin.
  • Seatwise asks for 8 permissions. Each one is needed by something it does.
  • Read Jira users: to see who is in Jira, which groups they are in and who has left. Also to find a new owner by name.
  • Read Jira work: to find each person's last Jira work, and to read spaces, filters, dashboards, permission schemes, space roles, components and plans. Also to check you are a Jira admin.
  • Write Jira work: to give the filters, dashboards, plans and open work items of someone who left to a new owner, when you choose to hand over.
  • Manage Jira projects: to make the new owner the space lead or component lead, and to take a leaver out of space roles. Jira also needs it to read work item security schemes.
  • Manage Jira configuration: this one is broad. Seatwise needs it to change group membership.
  • Seatwise uses it to take people out of seat groups when you remove them, and to add them back when you undo.
  • When you hand over, it also makes the new owner the default user of a field that named the leaver.
  • It also reads which groups give access, group members, notification schemes, work item security levels, workflows and field defaults. Seatwise changes nothing else with it.
  • Read Service Management requests: to list your service desks, so their queues can be checked for groups.
  • Store app data: check results, your settings, the history of changes and what Undo needs, inside Atlassian.
  • Report personal data: to tell Atlassian which accounts Seatwise stores, so their data is erased or updated when Atlassian says so.
  • Seatwise stores account IDs, display names and avatar links, plus facts about Jira use. It doesn't store email addresses or anything from work items.
  • Everything stays in the app's own storage on Atlassian's cloud. It follows your site's data residency.
  • About once a week, Seatwise tells Atlassian which accounts it stores. When someone closes their Atlassian account, Seatwise erases their data.
  • When someone's profile changes, Seatwise updates the stored name. The app's logs never contain names or account IDs.
  • After you uninstall, Atlassian deletes Seatwise's storage within 30 days. Seatwise keeps no copy anywhere else.
  • Questions about privacy or security: support@unitlane.net.

What you should see

You know what Seatwise can read and change, what it stores, and where.

If something is not right

Jira asks you to approve new permissions after an update. A Jira admin approves the update under Apps, then Manage apps. Until then, your site keeps the previous version.

You want to know what Seatwise changes in Jira. Only group membership, and for people who left: filter, dashboard and plan owners, space and component leads, field defaults, the assignee of their open work items, and space roles. Each change needs an admin's click and shows in History.

Still stuck? See Troubleshooting, or write to support@unitlane.net.