Community resources
Community resources
Community resources
Your Jira bill does not care whether anyone logged in
Most teams believe they pay for the people who use Jira. They do not. They pay for the people who have access to it, and those two groups drift apart quietly over years.
This is the sentence from Atlassian's own billing documentation that surprises people the most:
"Additional users are automatically counted towards billing even if they don't accept your invite or log in."
Read that again if you have ever justified a renewal on the basis that a tool is well used. Logging in is not part of the calculation. Someone invited in 2023 who never once opened Jira has been a paid seat ever since.
What actually stops the billing
Two things do, and the documentation is unambiguous about both:
- Removing the user. "You won't be billed for a user once they're removed."
- Suspending their access. "You won't be billed for a user when their access is suspended."
Notice what is not on that list. Deactivating someone in a connected directory, taking them off a project, stripping their permissions, or simply watching them stop logging in are not the same actions, and none of them are stated to stop the bill.
The gap the documentation leaves open
Here is the part worth knowing, and I would rather be straight about the limits of what is documented than pretend otherwise.
Product access in Atlassian Cloud is normally granted through a default product group. When you give someone access to Jira, they are added to that group, and the group is what carries the licence. Atlassian's pages on removing and suspending users state the billing effect of those two actions clearly, but they do not state whether revoking product access on its own, or removing someone from the product group while leaving the account in place, stops the billing.
That silence is the problem. It means the answer to "are we still paying for this person?" cannot be reasoned out from the documentation. It has to be checked against your actual bill.
If you have tested this on your own site and know the answer definitively, I would genuinely like to hear it, because it is the single most common source of confusion I see on this topic and there is a live discussion about exactly this problem in App Central.
Where the drift comes from
In practice, seats accumulate through ordinary, sensible-looking behaviour rather than negligence.
Offboarding that stops at the wrong layer. Someone leaves, IT disables their SSO account, and everyone considers it handled. Whether the Atlassian seat went with it depends on how your directory sync is configured, and nobody checks because the person has visibly gone.
Invitations that were never taken up. A team invites twelve people to a project. Eight join. Per the quote above, all twelve are counted.
Contractors and agencies. Access is granted for a three-month engagement. The engagement ends. The access does not, because nobody owns removing it.
Internal moves. Someone shifts from engineering to sales and stops using Jira entirely. They have not left the company, so no offboarding process fires at all.
None of these produce an error, a warning, or a single visible symptom. The only signal is a number on an invoice that is slightly larger than it needs to be, and it arrives once a year when nobody has time to interrogate it.
What to actually check
Before your next renewal, four questions are worth an hour:
- How many users hold product access, and how does that compare to the number who logged in during the last quarter? The gap between those two numbers is your answer. If you have never measured it, expect to be surprised.
- Which users have never logged in at all? These are the clearest wins, because there is no argument to have about whether someone might need it.
- Does your offboarding process actually remove or suspend the Atlassian user, or does it stop at the directory? Test it with one person who left recently rather than reading the runbook, because runbooks describe intentions.
- Who owns contractor access expiry? If the answer is nobody, that is where the persistent waste lives.
The wider version of this problem
Jira is the one you can see, because you administer it. The same drift is happening across every other tool your organisation pays for, and usually with less visibility, because those subscriptions were bought by people who no longer work there and renew on dates nobody tracks.
The pattern is identical every time: access outlives need, renewal is automatic, and the only moment anyone looks is after the money has already gone.
Closing
If you take one thing from this: stop treating "are people using it?" and "are we paying for them?" as the same question. Atlassian's documentation is explicit that they are not related, and the assumption that they are is what makes the waste invisible.
If your offboarding reliably closes the seat, I would be interested to know how you wired it up. Most of the setups I have seen close the account and quietly leave the licence behind.
Was this helpful?
Thanks!
Peter Hallander _Stackedboost_
6 comments