Topic starter
12/06/2026 12:18 am
TL;DR: SaaS management platforms differ less by spend control than by how they discover apps, automate joiner-mover-leaver workflows, and handle third-party access, according to 1Password. The governance issue is bigger than software cost because shadow IT, inconsistent offboarding, and incomplete access visibility create identity risk across SaaS, IAM, and compliance programmes.
Editorial analysis by NHI Mgmt Group, based on content published by 1Password: “Choosing the right SaaS management platform for your business”.
Key questions
Q: What breaks when SaaS spend management is treated separately from identity governance?
A: The organisation can remove licences without removing accounts, or keep accounts active without any clear business need.
Q: Why do SaaS discovery methods create different governance trade-offs?
A: Discovery based on expense data, logs, or browser telemetry produces different visibility and different privacy impact.
Q: How do teams know whether a SaaS management platform supports real offboarding?
A: A platform supports real offboarding when it can connect user removal to the actual app and entitlement, not just the identity provider record.
Practitioner guidance
- Define the primary objective first Decide whether the organisation needs spend optimisation, identity governance, or both before assessing platforms.
- Measure SaaS discovery coverage across the full estate Test how the platform finds apps through expense data, logs, browser telemetry, and other methods, then compare that coverage against the applications employees actually use.
- Check whether lifecycle workflows reach real revocation points Validate that onboarding, offboarding, access requests, and access reviews connect to actual entitlements and not only to the subset of apps already under SSO or SCIM.
Bottom line: The article argues that the real SaaS management question is whether the platform can govern access, not just report on spend.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
12/06/2026 9:28 am
Discovery is the first governance decision, not a convenience feature. A SaaS management platform only becomes useful for identity governance when it can expose shadow IT and map usage back to real users, not just invoices. If discovery is shallow, the organisation is optimising what it already knows instead of governing what employees actually use. The implication is that app visibility must be treated as a control requirement, not a reporting add-on.
A few things that frame the scale:
- 1 in 3 organisations encountered suspicious AI agent activity in 2025, and 99.4% experienced a SaaS or AI ecosystem incident.
A question worth separating out:
Q: When should organisations prioritise IAM coverage over licence optimisation in SaaS management?
A: Organisations should prioritise IAM coverage when hidden apps, delegated access, or weak offboarding create a larger risk than unused licences do. If the main concern is governance and compliance, access visibility and revocation matter more than squeezing the last percentage point out of spend reduction.
👉 Read our full editorial: SaaS management platform choice is an identity governance decision
This post was modified 1 day ago by NHI Mgmt Group