Unitlane Apps
Try RequestOps

Seatwise – Inactive Users, Licenses & Leavers for Jira

Find the Jira seats nobody uses.

See why each person costs a seat and what they still own. Remove seats safely, with Undo for 30 days, and hand over what leavers left behind. No API key needed.

Get it on Atlassian Marketplace Try it here
Free up to 10 users 30-day free trial One plan, everything included No API key No calls outside Atlassian

Seats nobody uses

See who costs a seat without using it

Open Seatwise and check your site. It tells you how many people have a Jira seat but haven't worked in Jira for 90 days, what they cost, and which groups give each one a seat.

  • Why each person costs a seat: the groups that give them Jira or Jira Service Management
  • Last Jira work: created, edited, moved, commented or logged time. Viewing Jira does not count, and Seatwise says so
  • What they still own: filters, dashboards, projects they lead and project roles
Seatwise Home: 31 people cost a Jira seat but haven't worked in Jira for 90+ days, about $3,199 a year, with the October checks. Sample data.

Safe cleanup

Remove seats safely, with Undo for 30 days

Preview who goes and who stays, and why. Seatwise removes people from the groups that give them Jira, shows what worked and what didn't, and lets you undo each removal for 30 days.

  • Only people who are ready to remove start ticked; the numbers always add up
  • A keep list and protected groups that Seatwise never touches
  • Try again for anything that failed, and a Recheck the next day
Seatwise cleanup preview: 25 people will lose their Jira seat, each with the groups they are removed from. Sample data.

Leavers

Hand over what leavers still own

People who left can still own filters, dashboards and projects that others use. Pick a new owner, hand it all over in one click and take them out of project roles. Seatwise lists what you change by hand.

  • Filters and dashboards get the new owner; projects get the new lead
  • Seatwise suggests a new owner when it can, or you search for anyone active in Jira
  • Filter subscriptions and other people’s private dashboards are listed as steps for you, because Jira does not let apps change them
Seatwise hand-over for one person who left: a suggested new owner and the filters, dashboards and project they still own. Sample data.

Groups

Know where a group is used before you change it

Seatwise lists empty groups that are used nowhere, and shows where every other group is used: permission schemes, project roles, filters, dashboards, issue security, workflows, notification schemes and service desk queues.

  • Atlassian's own groups are never suggested
  • Each place comes with a link
  • Places it cannot check are named: Automation rules, approvals in Jira Service Management, Assets and global permissions
Seatwise Groups: empty groups used nowhere, and a group opened to show the permission schemes, workflow, filters and project role that use it. Sample data.

Why a seat stays

A seat only goes when every path to Jira goes.

People often get Jira from more than one group. Remove one membership and the seat, and the bill, stay the same. Seatwise shows every path, so a cleanup actually frees the seat.

Marta gets Jira from two groups. One person, one seat, two paths to it.

Remove her from one group: the seat stays. The other group still gives her Jira, so nothing is saved yet.

Remove her from both: the seat is free. Seatwise shows every path, so you know which memberships have to go.

How cleanup stays safe

Accounts are never deleted or deactivated. Every step can be checked, and undone for 30 days.

  1. 1

    Preview first

    Every cleanup starts with a preview, sorted by outcome: who loses their seat, who is kept on purpose, who needs you first and who is new.

  2. 2

    You click Remove

    Seatwise acts as the admin who clicked. It never removes anyone on a schedule or by itself.

  3. 3

    An honest result

    Who was removed, who wasn't and why, with Try again for anyone that failed.

  4. 4

    Undo for 30 days

    Undo one person or a whole cleanup. Seatwise adds them back to the same groups.

  5. 5

    Recheck

    Seatwise rechecks the next day, or when you click Recheck now, and tells you if someone got Jira back.

  6. 6

    History and a renewal report

    Every change, who made it and the result. A one-page summary of seats freed for finance, saved as a PDF.

Try it here

The real Seatwise with a sample site. Click around: nothing you do here is saved or changed.

Open full screen
Open the app

Tap to open the real Seatwise with a sample site. Use your browser's Back button to come back.

Seatwise renewal report: seats freed, saving a year and people with Jira now, month by month. Sample data.
Renewal report. A one-page summary of seats freed and money saved, for finance or your manager.
Seatwise Settings: when a seat counts as unused, your plan and the keep list. Sample data.
Your rules. When a seat counts as unused, your plan and price steps, and a keep list with reasons.

Pricing

Free for sites up to 10 users. Above that, one plan priced by your Jira user count, billed through Atlassian Marketplace. 30-day free trial.

What do your inactive users cost? Try the free calculator

$40per month
$400 per year if billed annually

About $0.40 per user per month

Start the 30-day free trial
Price per user per month, by part of your user count
UsersPer user per month
1 to 10 usersFree
11 to 100 users$0.40
101 to 250 users$0.25
251 to 1,000 users$0.20
1,001 to 2,500 users$0.12
Above 2,500 users$0.08

Each user is charged at the rate for their part of the count; the annual price is 10 times the monthly price. Prices in US dollars, before tax. Atlassian Marketplace shows the exact price for your site.

Built on Atlassian. Nothing leaves it.

Seatwise runs on Atlassian Forge and asks for no API key. It makes no calls to servers outside Atlassian, and the user export is read in your browser, never uploaded as a file. Only Jira admins can open it.

What it can't do

  • It does not deactivate or delete Atlassian accounts, and it does not manage Confluence seats. Work items, comments and history stay exactly as they were.
  • It does not remove people on a schedule. Jira only lets a site admin change group membership, so a person always clicks Remove.
  • It cannot change groups that your identity provider manages (for example Okta or Microsoft Entra ID). Seatwise marks those groups and tells you to change them there.
  • "Last Jira work" is not a login date. Someone who only reads Jira looks inactive until you add Atlassian's user export, which Seatwise reads in your browser.
  • Money figures use the seat price you enter once in Settings; Atlassian does not tell apps your price. Savings are estimates, not a promise.

The 8 permissions, and why

Read Jira users
See who is in Jira, which groups they are in and who has left, and find a new owner by name.
Read Jira work
Find each person's last Jira work, and read the projects, filters, dashboards, permission schemes and project roles they are part of.
Write Jira work
Give the filters and dashboards of someone who left to a new owner, when you click Hand over.
Manage Jira projects
Make the new owner the project lead and take the person who left out of project roles, when you click Hand over.
Manage Jira configuration
Jira only lets an app change who is in a group with this permission: to remove people when you click Remove, and add them back when you click Undo. Apart from group membership, Seatwise changes nothing with it.
Read Service Management requests
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
Tell Atlassian about once a week which accounts Seatwise stores, so their data is erased when someone closes their Atlassian account and updated when their name changes.

Questions

Does it delete or deactivate accounts?

No. Seatwise only removes people from the Jira groups that give them a seat, and only when an admin clicks Remove. Accounts, work items, comments and history stay. You can undo for 30 days.

Do I need an API key?

No. There is nothing to set up. The first check reads Jira’s own work history. Nothing leaves Atlassian.

Why is there no exact last-login date?

Jira does not give apps a last-login date. Seatwise shows each person’s last Jira work instead. For the exact "last seen" date, add Atlassian’s user export from admin.atlassian.com; Seatwise reads it in your browser and keeps only each person’s account ID and last-seen date.

Does it work with Okta, Microsoft Entra ID or other SCIM groups?

Seatwise reads them and shows who gets a seat from them. It cannot change them: Jira does not let apps change groups that your identity provider manages. Seatwise marks them and the rest of the cleanup still runs.

Can it remove inactive users automatically on a schedule?

No. Jira allows group changes only by a site admin, so an admin always clicks Remove. Seatwise checks your site every day and every month, and tells you what is new.

Who can use it?

Jira admins can open Seatwise and see everything. Removing people from groups also needs a site admin, because that is Jira’s rule.

Does it cover Jira Service Management agents and Confluence?

Jira Service Management agents, yes: they are counted as seats. Confluence, no.

How does it know what I pay?

Atlassian does not tell apps your plan or price. Enter your seat price, billing, renewal date and price steps once in Settings. Seatwise then shows savings and how many people to remove to reach the next lower price step at renewal.

What does it cost?

Free up to 10 users, then one plan priced by your Jira user count, with a 30-day free trial. Everything is included.

How do I get help?

Email [email protected], Monday to Friday, European business hours.

Stop paying for seats nobody uses.

Free up to 10 users. 30-day free trial for bigger sites.

Get it on Atlassian Marketplace Try it here