Last updated: November 21, 2026
Software license management is the work of tracking which software licenses your company pays for, who holds each one, whether they use it, what it costs and when it renews. You then reclaim or right-size the seats nobody uses. For SaaS, the most reliable usage signal is login data from your SSO or identity provider, checked against vendor admin data.
The term also covers installed desktop software and the vendor side of licensing (how software makers issue and enforce keys). This guide is about the buyer side, for SaaS, and it goes deep on tracking and monitoring: the fields to record, the four places usage data comes from, the alerts worth setting, and a reclamation process that runs without a quarterly cleanup project.
Two related guides cover the rest. How to manage SaaS licenses walks through the full six-step program, from inventory to renewal reviews. The 10 SaaS management platforms compares the tools.
Key Takeaways:
- Track six things per app: seats bought, seats assigned, last login per user, cost per seat, renewal date and owner.
- SSO login data is the cheapest usage signal, but it shows sign-ins, not real work. Check high-cost apps against the vendor's own admin data.
- Monitoring means alerts on thresholds. A report you read once a quarter is an audit, not monitoring.
- Reclaiming a seat saves nothing until you lower the purchased seat count at renewal.
- Organizations leave an average of 36% of their SaaS licenses unused, according to Zylo's 2026 SaaS Management Index.
What should you track for every software license?
A license record needs enough data to answer two questions: is this seat being used, and what happens if we remove it? Here are the fields that answer both.
The last row gets skipped most often, and it decides how much work reclamation will be. If an app gets its users from an identity provider group, removing a seat is one group change. If someone added users by hand in the vendor console, someone has to remove them by hand too.
Why most software license tracking efforts break down
License tracking breaks down when the data and the action live in different places. Finance knows the cost. The identity provider knows who signs in. The vendor console knows the seat count. The approval to add the user sits in a Jira ticket or a Slack thread.

Visibility without action is still waste
A usage report that finds 40 inactive users is a to-do list. Someone still has to confirm the list with the app owner, ask the users, remove each one in the identity provider, record the change and then lower the seat count at renewal. If each step needs a person to start it, most of the list never gets done and the company keeps paying. Policy-based SaaS cost optimization runs those steps on its own.
How to track software license usage: four data sources
No single source tells you everything. Each answers a different question, and each has a gap.
Start with identity data, not app-by-app detective work
If your apps sign in through Okta, Microsoft Entra ID or Google Workspace, you already have usage data for most of your stack. As of November 2026, Okta's Application Access report lists single sign-on attempts per app (the user.authentication.sso event) and exports to CSV. Microsoft Graph exposes a lastSuccessfulSignInDateTime property for each user, which Microsoft recommends for inactive-user reports.
Know the limits before you act on the data:
- A sign-in is not usage. A user whose session stays open for weeks may show one login a month and still work in the app every day.
- Apps outside SSO are invisible. If people sign in with a local password, the identity provider never sees them.
- Directory sign-in and app sign-in are different. Entra's
signInActivityrecords sign-ins to the directory. To know whether someone used Salesforce, look at the app's own sign-in events.
For most collaboration and productivity apps, 30 to 90 days with no SSO sign-in is still a strong enough signal to start a reclamation warning. For your ten most expensive apps, confirm the signal against the vendor's data first.
Check expensive apps against vendor admin data
Many business SaaS products show a last active date per user in their admin console, and many expose it through an admin API. This data is closer to real usage than an SSO event, and it also shows the license tier, so you can spot a premium seat on someone who only views files.
The cost is effort. Every vendor has a different console, a different API and often a plan requirement for usage reports. Pull vendor data for the apps where seats are expensive or the contract has a true-up clause. For the rest, SSO data is enough.
Use finance data to find what you pay for
Card statements, expense reports and accounts payable show apps that never went through IT. Those apps have no SSO data, no owner and often several overlapping subscriptions. Zylo's 2026 index found that expense-based SaaS spend rose 267% year over year. Finance data won't tell you who uses a tool, but it tells you which tools to put in the inventory and connect to SSO.
Ask users before renewals
A short survey ("Do you still use this?") two months before a renewal catches what logs miss. Someone who reads reports in a BI tool once a quarter may look inactive and still need the seat. Treat non-responders as a signal too. Send a reminder, then flag the seat for review if the user still doesn't answer.
Software license monitoring: from reports to alerts
Tracking tells you the state of your licenses today. Monitoring means checking that state continuously and alerting someone when it crosses a line. Monitoring is how you find waste in week two instead of month eleven.
What to alert on
- A user has no sign-in to an app past that app's inactivity threshold.
- A user left the company or changed roles and still holds a paid seat.
- Assigned seats exceed purchased seats, which risks a true-up charge.
- A renewal date falls inside its notice period and nobody has reviewed the seat count.
- A new app shows up in expense data with no owner and no SSO connection.
- A user holds an admin or premium tier and has only used basic features.
Set thresholds by how people use the app
One threshold for every app produces false alarms. Base it on the normal rhythm of each tool:
Exclude the accounts that shouldn't be reclaimed on inactivity, such as executives who sign in rarely, people on leave and service accounts. For more on picking thresholds, see how to monitor inactive users for SaaS license optimization.
A license reclamation process that runs on its own
Monitoring finds unused seats. Reclamation removes them. The process below works whether you run it by hand or automate it.
Treat reclamation like an always-on policy, not a campaign
- Set a policy per app. Inactivity threshold, warning period, exclusions and who gets notified.
- Warn the user. Say which app, how long they have been inactive and when access will be removed.
- Give a grace period. Seven to fourteen days catches people who were traveling or on leave. A sign-in during the grace period cancels the removal.
- Remove access through the identity provider. Take the user out of the group that grants the app, so the change is recorded and reversible.
- Record the change. Write the reason, the date and the removal to a ticket, so the next audit or a "why did I lose access" question takes seconds to answer.
- Return the seat or lower the count. A reclaimed seat goes back to the pool for the next request. At renewal, cut the purchased count to match what you actually use.
Step 6 is the one teams forget. On an annual contract, removing 40 users from Figma saves nothing until you buy 40 fewer seats. Bring the usage data to the renewal conversation. This contract renewal playbook covers how.
Make every access grant easier to unwind
The cheapest seat to reclaim is one that was set up to end. When someone asks for an app for a project, an audit or an incident, grant it for a fixed window with time-based access and let it expire. Then no warning, grace period or reclamation step is needed later.
Before you grant any paid seat, decide three things: which identity provider group grants it, whether it should expire, and which inactivity threshold applies. If you answer those when you grant access, the seat already has a removal rule when it goes idle.
Types of software license management tools
Four kinds of tools handle license tracking, and most license monitoring software falls into one of them. Which one fits depends on where your access work already happens.
If you need to discover apps across a large company with heavy shadow IT, start with a SaaS management platform. Our comparison of 10 SaaS management platforms covers Zylo, Torii, Zluri, ServiceNow and six others. If your access requests already run through Jira Service Management, an ITSM-based tool keeps license work next to the tickets that granted the access.
How Multiplier turns license tracking into enforced action
Multiplier is an identity governance and access management app that runs inside Jira Service Management. For licenses, it reclaims unused SaaS seats based on login activity or user surveys, and records each step on a Jira ticket.

Usage-based reclaim tied to Jira and your identity provider
License reclamation tracks login activity across your SaaS stack. You configure a policy once per app: how many days of inactivity trigger a warning, how long until revocation, and who gets notified. Inactive users get a warning. If they stay inactive, Multiplier revokes the license automatically and records the change on a Jira ticket.
Before a renewal, License Optimization can run a survey asking users whether they still use the app. Responses feed the reclamation workflow. Non-responders get reminders, then get flagged, so you know how many seats to renew.
Temporary access, cleaner reviews, and a better request path
The same app handles the requests that create seats in the first place. Employees pick sanctioned apps and roles from a catalog in the JSM portal or Slack, approvers decide in Jira or Slack, and time-based access removes short-term seats when the window ends. Access reviews run in JSM too, and a reviewer's Revoke decision removes the access.
Automatic license reclamation ("Auto Reclaim Licenses") is part of the Advanced plan at $6 per user per month. Standard is $5 per user per month and covers access requests, access reviews and lifecycle workflows. Both plans have a 30-day free trial with no credit card. See pricing for details.
Start a free trial of Multiplier on the Atlassian Marketplace
Frequently asked questions
What is license management software?
License management software keeps a record of the software licenses a company owns and shows who holds each one, how often they use it, what it costs and when it renews. Buyer-side tools for SaaS read usage from SSO, vendor APIs and finance data, then help reclaim unused seats. Endpoint tools track installed desktop software. Vendor-side tools issue and enforce license keys for software makers.
What is the best software for license management?
It depends on where your access work happens. Large companies with heavy shadow IT usually start with a SaaS management platform such as Zylo or Torii. Teams that run access requests through Jira Service Management can keep reclamation in the same tickets with an app like Multiplier. If most of your licenses are installed desktop software, an endpoint software asset management tool fits better.
How do I automate software license management?
Connect your apps to an identity provider so sign-in data and group membership sit in one place. Then set a reclamation policy per app with an inactivity threshold, a warning, a grace period and automatic removal from the identity provider group. Log each removal to a ticket. Add surveys before renewals for apps where sign-in data is a weak signal of real use.
What is the difference between software license tracking and monitoring?
Tracking records the current state: seats bought, seats assigned, who holds them and when each user last signed in. Monitoring checks that record continuously and alerts someone when a threshold is crossed, such as a user inactive for 60 days or a renewal entering its notice period. You need tracking first. Monitoring turns the tracking data into action while savings are still possible.
How many days of inactivity should trigger license reclamation?
Base it on how often people normally use the tool. Thirty days fits daily tools like Slack or Zoom. Forty-five to 60 days suits weekly tools such as design or CRM apps. Use 60 to 90 days for specialist or periodic tools. For apps used once a quarter or once a year, ask users in a survey before renewal instead of reclaiming on inactivity.
Does SSO login data show real software usage?
Partly. SSO data shows when someone signed in to an app, not what they did there. Long sessions can make an active user look idle, and apps that accept local passwords never show up. It is still the cheapest usage signal for most of your stack. For expensive apps or contracts with true-up clauses, confirm it against the vendor's own last-active data before removing seats.





