Topic starter
11/06/2026 11:43 pm
TL;DR: Tracking SaaS licenses is less about cost control than governance, because manual spreadsheets, employee surveys, ITAM, and SAM all miss parts of the software stack, according to Zluri. The real issue is that fragmented discovery leaves shadow IT, unused licenses, and offboarding gaps visible only after spend and access have already drifted.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “How to Track Software License”.
Key questions
Q: What breaks when SaaS access reviews rely on spreadsheets?
A: Spreadsheets freeze access data in time, so reviewers work from stale exports while roles, teams, and app usage keep changing.
Q: Why do ITAM and SAM miss shadow IT in SaaS environments?
A: They miss it because they were built around hardware and on-premise software, not browser-delivered subscriptions created outside traditional procurement flows.
Q: How can teams tell whether SaaS governance is actually working?
A: Look for evidence that discovered applications can be assigned an owner, tied to an access policy, and removed through an enforced workflow.
Practitioner guidance
- Adopt multi-source SaaS discovery Correlate SSO, identity provider, HR, finance, app integrations, and user activity signals into one entitlement inventory so hidden apps do not escape governance.
- Retire spreadsheets as the control point Keep spreadsheets only as a transitional reference and move renewal, ownership, and offboarding decisions into a governed system of record.
- Tie revocation to lifecycle events Trigger license removal when employees leave, change roles, or no longer need an application, instead of waiting for periodic clean-up cycles.
Bottom line: SaaS license tracking is really a governance problem because incomplete discovery leaves shadow IT, unused licenses, and offboarding gaps outside control.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
12/06/2026 8:31 am
Shadow IT is an identity governance failure before it is a cost problem: The article makes clear that unmanaged SaaS adoption begins when users can create access outside the controlled lifecycle. That means the organisation loses ownership of the joiner, mover, and leaver state for those apps, so governance never sees the entitlement until after spend and exposure have already accumulated. Practitioners should treat discovery completeness as a core identity control, not a procurement detail.
A question worth separating out:
Q: How should organisations govern SaaS licenses as part of IAM and IGA?
A: Treat SaaS licenses as governed entitlements, not just commercial line items. Link each license to an owner, a business purpose, and a review cadence so access can be validated, reclaimed, or retired when the need changes. That approach reduces shadow IT and prevents dormant access from surviving contract renewals.
👉 Read our full editorial: SaaS license tracking exposes the governance gap in shadow IT
This post was modified 4 days ago by NHI Mgmt Group