Since 2009
TELCOMA Global / License Audit for Confluence / Documentation
Find the Confluence seats nobody is using.
License Audit lists the licensed users on your Confluence Cloud site who have contributed nothing in Confluence for a period you choose, so you can decide which seats to reclaim. It is read-only: it never removes anyone's access and never changes anything on your site. There is nothing to configure — no API key, no organisation token, no groups to name.
Install
Three steps, all inside Confluence.
Find the app
In Confluence go to Settings → Atlassian marketplace → Find new apps and search for License Audit for Confluence.
Start the trial
Click Try it free. A 30-day trial starts automatically and rolls into a subscription unless you cancel from Manage apps.
Approve the permissions
Every one is a read permission. The app requests no write access of any kind.
Only Confluence administrators can open the app. Find it under Confluence administration → Settings → Apps → License Audit.
Run an audit
Pick a period. Press the button. Come back when it's done.
- Choose a period: No contribution in 30, 60, 90, 180 or 365 days.
- Click Run audit.
- Keep the page open for a few seconds while the app lists your users — that step runs as you, so it sees exactly the users you can see. After that the scan continues in the background: you can close the page, and the result is waiting when you return. On a large site expect a few minutes.
You'll see progress through three stages: listing licensed users, scanning recent contributions, and verifying candidates.
Read the report
One number you already pay for, and the list behind it.
The summary line
Licensed users are the accounts Atlassian counts for Confluence on your site — the same figure as Users for Confluence in Atlassian Administration. Apps, deactivated accounts and guests are excluded; guests hold no licence. Beside it: how many were active in the period and how many are inactive.
The inactive list
Each user with their email (where their profile allows) and their last contribution: 90–180 days, 180–365 days, or over a year, or never. Sorted longest-inactive first.
Enter the yearly price of one seat and press Save price: the page then leads with how many seats are inactive and about what they cost a year. The price is kept for your site, so the figure is there on every visit. Search by name or email and filter by how long someone has been inactive; filters cover the whole list, not one page. Download CSV or Download Excel gives you every inactive user, ready to hand to whoever manages licences.
Ask Rovo
Ask about your seats in plain words.
License Audit includes a Rovo agent. In Confluence, click Ask Rovo, open the agent list and choose License Audit for Confluence. It answers from the latest audit report, with names, inactivity and cost. Open it from Confluence: in Rovo inside Jira its tools aren’t available.
Try asking
“How many Confluence seats are unused, and what do they cost a year?” · “Who has contributed nothing for over a year?” · “How is an inactive user decided?”
What it won't do
It only reads. It can't remove anyone's access or run an audit; run audits from the app page. Only Confluence administrators get answers.
Answers come from Atlassian Rovo and count toward your site's Rovo allowance, like any other agent.
How inactivity is decided
A user is listed only if they contributed nothing in Confluence.
A contribution means any of the four actions below. Two rules follow, and they are the reason the list can be trusted.
Created or edited a page or blog post — including a whiteboard or database.
Posted or edited a comment, inline or at the foot of a page.
Uploaded a file or a new version of one.
Reading pages doesn't count. Confluence doesn't let apps see who read what, so a contribution means creating, editing or commenting.
The app first scans recently modified content to prove most users active quickly, then runs a dedicated check for anyone it couldn't vouch for — including the full edit history of pages other people changed since, so a colleague editing your page never makes you look active, and never hides you either. A name reaches the list only after that check finds nothing.
Someone who only reads Confluence will appear on the list, because reading leaves no trace an app can see. Before removing a seat, check that person's last active date in Atlassian Administration. Treat the report as the shortlist for that check, not as a list of people to remove.
Your data
Nothing leaves Atlassian.
The list of accounts that can use your site, their status, and the author and time of recent page, blog post, comment and file changes. It does not read page text, comment text, attachment contents or titles.
Only account IDs, inactivity bands, your seat price and scan progress, in Atlassian's own storage for your site. Names and emails are looked up live when you open the report. No page content, ever.
Nowhere. The app has no servers of its own and makes no requests outside Atlassian. If you use the Rovo agent, Atlassian Rovo writes the answer, inside Atlassian.
Everything the app stored is deleted.
Full details in the privacy policy.
Frequently asked
The questions admins ask first.
Someone is listed who I know uses Confluence every day.
Check what they do. If they only read pages, they leave no trace Confluence can report — no app can see logins or page views. Confirm with their last-active date in Atlassian Administration. If they created, edited, commented or uploaded something in the period and still appear, send us their display name and the period and we'll investigate.
Someone is listed who only uses Jira.
Correct — the app measures Confluence contributions only. A Jira-only user holding a Confluence seat is exactly a seat worth reviewing.
The licensed-user count is not what I expected.
It is the number of accounts that can use your Confluence site, excluding apps, deactivated accounts and guests. It should match Users for Confluence in Atlassian Administration. If it doesn't, tell us both figures.
Why are emails missing for some users?
Their Atlassian profile privacy settings hide the email. Name and account ID are still shown.
A scan failed with a permission error.
Click Check permissions. The app tests each call it needs and names the permission that was refused. Updating the app from Manage apps re-grants every permission — this happens when an update added a permission that has not yet been accepted.
The scan says "stuck". Is something wrong?
If a scan makes no progress for 20 minutes the app offers to restart it. Restarting is safe: a scan never changes anything on your site.
Can the app remove the inactive users for me?
No, by design — it holds no write permission, so Confluence itself prevents it from changing anything. Reclaim seats in Atlassian Administration, with the list in hand.
How is it priced?
Free for sites with up to 10 users. Larger sites pay per user per month, billed by Atlassian on your existing invoice, after a free 30-day trial. The current price is on the Marketplace listing.
Support
Ask the people who built it.
When reporting a problem, include your site URL, the period you ran, and — for a wrongly-listed user — their display name. We never need passwords or tokens.
Get help
One business day, usually much less.
- [email protected]
- Support page
- Known limits, what to include, status
- Response time
- Within one business day