You Are Probably Paying for Jira Seats Nobody Uses

Ask a Jira admin how many of their licensed users are active and you will usually get a confident number. Ask them how they know, and the answer gets vaguer.

Seats leak quietly. A contractor finishes a project and nobody remembers to remove them. Someone moves to a team that lives in a different tool. A manager who once needed Jira for one quarterly review still holds a licence two years later. None of these feel like a problem on the day they happen, and every one of them shows up on the next renewal.

Why the leak is hard to see

Atlassian bills on the number of users with product access, not on who actually does anything. The admin console tells you who has access. It is much less helpful about who used it, and joining "has a seat" to "has done something in Jira lately" across a few hundred accounts is the kind of spreadsheet job that gets postponed until the invoice arrives.

There is also a reason admins hesitate even when they suspect waste: removing the wrong account hurts. Deactivate a service account and an integration stops. Deactivate someone with open work and their issues are orphaned in the middle of a sprint. So the cautious default is to leave everything alone, and the bill keeps growing.

What LicenseGuard does about it

LicenseGuard for Jira does the joining for you. It scans your site and sorts every account into Active, Dormant or Ghost based on Jira activity, using thresholds you choose. It then puts a number on it: what those inactive seats are costing you each year.

The part we care about most is the safety net. Before you act on anything, LicenseGuard flags the risky accounts, such as admins and users who still have open work assigned. You can safelist service accounts and anyone who must stay, so they never show up as candidates again.

When you have reviewed the list, LicenseGuard takes you straight to Atlassian's admin console to deactivate the accounts you picked. It does not remove anyone by itself, on purpose: the final click stays with a human in Atlassian's own tool, and every safelist change and hand-off is recorded in an activity log with a timestamp and the admin who made it.

Scans can run weekly or monthly, and the dashboard tracks inactive accounts and savings over time, so the clean-up does not have to be a once-a-year scramble before renewal.

Free, and it stays inside Atlassian

LicenseGuard is free, with every feature included. It runs on Atlassian Forge, so there are no external servers and no data leaves your Atlassian tenancy. We wrote about why we made it free earlier this year.

Getting started

1. Install it from the Atlassian Marketplace and pick your Jira site.
2. In Jira Settings, go to Apps and open LicenseGuard. You need to be a site admin.
3. Run a scan, safelist who must stay, and review the rest.

The setup guide walks through each step with screenshots.

---

LicenseGuard is one of four Jira apps we have live on the Atlassian Marketplace. See them all, or talk to us if you need something built for your own Jira.