Topic starter
12/06/2026 12:55 am
TL;DR: SaaS management platforms are presented as a way to discover shadow IT, rightsize licenses, and improve onboarding, offboarding, and compliance, according to Zluri. The governance issue is broader than SaaS cost control: unmanaged app access is also an identity lifecycle problem that weakens visibility, accountability, and deprovisioning discipline.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “How to Convince Your Boss to Invest in an SMP?”.
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 does SSO not solve SaaS access governance on its own?
A: SSO centralises authentication, but it does not eliminate app-local licenses, OAuth tokens, file ownership, or external sharing links.
Q: What should teams get wrong about offboarding in SaaS environments?
A: They often assume disabling the primary account is enough.
Practitioner guidance
- Map the SaaS estate from application data Build an inventory from direct integrations, usage data, and admin sources so approved, redundant, and shadow applications are visible in one place.
- Tie offboarding to application-level revocation Remove access at the application boundary when users leave, then verify that licences are transferred or cancelled rather than left active.
- Use renewal review as an access control checkpoint Treat contract renewal as a governance event that checks whether the application is still needed, who owns it, and whether current users still require access.
Bottom line: SaaS management platforms address a governance blind spot by revealing apps, users, and entitlements that are invisible in manual tracking.
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 10:29 am
Shadow IT is an identity governance problem before it is a SaaS cost problem. The article frames discovery and cost optimisation as the visible benefits, but the deeper issue is that unmanaged applications also mean unmanaged access relationships. If the application is outside governance, so are approval, ownership, review, and offboarding discipline. Practitioners should treat SaaS discovery as a control map for the identity lifecycle, not as a procurement report.
A question worth separating out:
Q: When should organisations prioritise SaaS management over spreadsheet-based tracking?
A: They should prioritise it once the number of apps or users makes manual tracking unreliable. If the organisation cannot answer which apps are approved, which are redundant, and who still has access, the process has already outgrown spreadsheets and needs governed automation.
👉 Read our full editorial: SaaS management platforms expose the governance gap in shadow IT
This post was modified 4 days ago by NHI Mgmt Group