Topic starter
11/06/2026 11:25 pm
TL;DR: Manual SaaS onboarding breaks down as employee app usage climbs past 100 applications on average, leaving IT teams with repetitive provisioning, shadow IT risk, and incomplete access coverage, according to Zluri. The real issue is not speed alone but whether onboarding workflows preserve governance while scaling access decisions.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “4 Ways of Giving Quick Access to Tools While Onboarding Employees”.
By the numbers:
- Today, an employee in a mid-size company uses over 100 apps on average.
- Using an SSO, you can give access to only 30% of the required SaaS tools.
Key questions
Q: Why does manual onboarding become risky as the SaaS estate grows?
A: Manual onboarding becomes risky because the number of apps, accounts, and access rights grows faster than teams can reliably manage them.
Q: How should teams handle SaaS apps that are not covered by SSO?
A: Teams should treat non-SSO applications as a separate governed population, not as exceptions to ignore.
Q: What are the signs that SaaS onboarding is not under control?
A: Common signs include employees waiting days for basic access, frequent one-off provisioning requests, users signing up for tools on their own, and disagreement about which applications are actually in use.
Practitioner guidance
- Build a live SaaS inventory Continuously discover the applications actually used in the organisation before attempting to automate onboarding or access requests.
- Map coverage gaps outside SSO Identify the SaaS tools that cannot be reached through single sign-on and assign a separate provisioning path for them.
- Standardise role-based onboarding playbooks Create repeatable onboarding workflows that use department and seniority signals to provision the common access set consistently.
Bottom line: Manual SaaS onboarding breaks down because it cannot keep pace with a growing and changing application estate.
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:03 am
Manual onboarding is really an inventory problem disguised as an access problem. If teams do not know which SaaS applications are in use, they cannot credibly say onboarding is complete. The article’s strongest point is that access gaps often start before provisioning, at discovery and classification. That makes inventory the prerequisite control for any scalable onboarding programme.
A question worth separating out:
Q: What breaks when fraud investigations depend on spreadsheets and ad hoc team pings?
A: The main failure is latency. By the time someone gathers the numbers, the signal may have gone cold and the fraud pattern may have shifted. That slows investigation, hides the orders driving the issue, and makes executive reporting stale. Teams also lose consistency, because different analysts may assemble different views of the same problem.
👉 Read our full editorial: SaaS onboarding automation exposes the limits of manual access control
This post was modified 4 days ago by NHI Mgmt Group