Software asset management works better when IT closes the loop

When every employee uses dozens of apps with different owners and separate admin consoles, it’s easy to miss a paid seat during offboarding. And if you don’t catch the empty seat until the next renewal, you’ve essentially paid for a license no one used.

Software asset management (SAM) helps you track what your company pays for and whether it’s still needed. But identifying an unused license isn’t the same as freeing it up. IT needs to remove the access and make sure the seat is available for someone who’s actually on the payroll.

Here’s what SAM tools handle and how an ITSM platform helps your team follow through.

How ITSM helps put your software asset management findings to work

A software asset management tool flags a license you don’t need, but IT still has to do something about it. That might mean removing access after an employee leaves or reclaiming a seat someone hasn’t used in months. IT service management (ITSM) gives your team a way to handle that work alongside the access requests and support tickets already coming through the help desk.

Serval is an AI-native ITSM platform with access management built in. Here’s what pairing an ITSM tool like Serval with a SAM platform can help you do.

Reclaim unused seats without waiting for someone to leave

An employee doesn’t have to leave for a license to go unused. Their project can end or they may switch tools without returning the seat. That unused access continues to cost money until IT removes it.

There are two ways Serval supports reclaiming that access:

• Ongoing reclamation: Serval’s access management syncs last-login data from connected applications or the identity provider to find access that’s gone unused past a threshold IT sets. Qualifying access can be reclaimed automatically or sent to a reviewer for a decision, and audit trails record the removal so IT can trace what happened. If last-login data is missing, Serval skips the grant instead of assuming it’s unused.
• Reclamation during employee changes: Access management can revoke application access when someone leaves or changes roles. This frees the associated seat where the application’s licensing model allows it. As part of your employee onboarding and offboarding, Serval journeys can coordinate those removals across applications so old permissions don’t follow employees to new jobs.

Both approaches remove access after it’s no longer needed. But with an ITSM platform like Serval, IT has another option when they know the end date up front: Serval’s just-in-time (JIT) access provisioning lets the team schedule removal as part of the original request. Access for a two-week project expires when the work ends instead of sitting around long enough to qualify for reclamation.

Give IT the asset context to resolve the ticket

When someone asks for a software license, IT shouldn’t have to open five admin consoles to find out whether there’s an unassigned seat they can use. Using ITSM to connect asset management data to the ticket gives the help desk a place to start.

Serval’s databases bring records from connected systems into a shared view. IT can see which licenses belong to an employee and check seat availability when that information is included in connected records. It also supports broader asset tracking by combining data from mobile device management (MDM) and procurement tools with identity records. Teams choose the authoritative source for each field and retain a history of changes.

The help desk can then check for an available seat before treating the request as a reason to buy another one.

Keep access records and licensing obligations straight

Knowing who has a license doesn’t tell you whether you’re meeting the vendor’s licensing terms. And removing someone’s access doesn’t settle what you owe at renewal.

Serval handles access operations and brings asset context into IT work. Its inactivity-based reclamation isn’t software usage metering. Its Software & Licensing database also tracks entitlements, seats, and contracts, and records whether each product is compliant, under-licensed, or over-licensed.

A dedicated software asset management tool adds software discovery across devices, usage metering, and the licensing analysis vendor audits require. Serval’s ITSM capabilities complement that work by coordinating access changes and surfacing connected asset context while the SAM tool supports broader discovery and vendor audits.

What a SAM tool owns

Software asset management is the software side of IT asset management (ITAM), which also covers hardware. A SAM tool helps establish what software your company has and what it’s entitled to use. Enterprise asset management software can cover a broader range of physical assets, so it’s worth checking the scope behind the label.

In SAM tools, discovery builds the inventory and can uncover shadow SaaS where supported. The tool then compares deployments and usage against purchased entitlements. Having 200 licenses doesn’t necessarily mean you can install the software on 200 machines: The contract determines what’s allowed.

That comparison helps IT spot licensing shortfalls and spending it can cut. It also provides evidence for vendor audits and gives Finance and Procurement a clear view before renewal talks begin.

But IT still needs to act on those findings, whether that means removing an installation or reclaiming access before buying another seat. How that happens depends on the SAM tool’s automation capabilities and the systems it connects to.

How the roles of SAM and ITSM platforms differ

Different platforms collect similar asset data, but each one uses that information for a distinct part of the workflow. The key difference is how the system turns those records into licensing insight or operational action. When comparing options, look at what each platform does with the data it collects. The following table shows how several top platforms approach that work:

Start with the gap you need to close. Uncertainty about licensing terms calls for SAM capabilities. Unused access lingering after a decision calls for reliable execution. You may decide your team needs both.

How Serval fits alongside your software asset management tool

A SAM tool helps you make licensing decisions. Serval helps IT follow through, providing ongoing reclamation of inactive access and coordinated removal when employees leave or change roles. Serval’s databases also help teams manage assets using connected records that bring context into support tickets.

Book a demo to see how Serval helps IT reclaim unused access before another renewal rolls around with ghosts still on the bill.

FAQ

How can IT teams reclaim software license spend during offboarding?

Remove the departing employee’s application access and confirm which paid seats can be reassigned. Update the license inventory so IT checks those seats before purchasing more. Reclamation supports software license management, but immediate savings depend on whether the subscription allows seat reductions mid-contract or only at renewal.

Can an ITSM platform replace a dedicated SAM tool?

It depends on how much licensing analysis you need. Serval’s Software & Licensing database tracks entitlements, SaaS seats, contracts, and renewals and flags products as compliant, under-licensed, or over-licensed, and its access management reclaims inactive access and removes access when employees leave or change roles. Teams that need software discovery across devices, usage metering, or vendor audit support can run a dedicated SAM tool such as Flexera alongside Serval.

How does connecting SAM and ITSM improve software visibility?

SAM provides visibility into software deployment and usage alongside license entitlements. Connecting those records to IT service management (ITSM) helps teams carry that context through the employee lifecycle. Automated access changes and recorded outcomes give IT evidence to check during an audit, while the SAM tool supports compliance with vendor licensing terms.

How does access revocation fit into joiner-mover-leaver workflows?

Employees need access when they join and different permissions when they change roles. When they leave, access needs to end altogether. Revocation keeps old permissions from accumulating across those transitions. It supports software lifecycle management by freeing assigned seats for reuse while the SAM tool continues to track the associated licensing obligations.