Topic starter
11/08/2026 3:24 pm
TL;DR: Managed service providers are under pressure to govern multiple client SaaS environments, with Josys arguing that centralised visibility, automated provisioning, and continuous monitoring can reduce operational strain and improve compliance reporting. The real issue is that MSP identity governance still depends on tenant-by-tenant control discipline, not just a unified console.
Editorial analysis by NHI Mgmt Group, based on content published by Josys: “How Josys Helps MSPs Govern Identity and Secure SaaS Operations at Scale”.
Key questions
Q: How should MSPs govern SaaS access across multiple client tenants?
A: MSPs should treat SaaS access as a tenant-specific governance problem, not a single shared admin task.
Q: Why do SaaS dashboards fail as a substitute for identity governance?
A: Because dashboards describe activity, but they do not enforce policy.
Q: What are the signs that MSP SaaS governance is out of control?
A: Common indicators include mismatched licence counts, unclear ownership for client apps, delayed offboarding, and inconsistent access decisions across tenants.
Practitioner guidance
- Standardise tenant-by-tenant access workflows Define one repeatable model for provisioning, deprovisioning, and policy enforcement, then apply tenant-specific exceptions explicitly rather than informally.
- Separate visibility from approval authority Use the central dashboard for coordination and evidence, but keep entitlement approval rules tied to each client’s governance requirements.
- Operationalise least privilege across every client Review permissions and subscriptions tenant by tenant so shared administration does not leave overbroad access in place by default.
Bottom line: MSP SaaS governance becomes fragile when a central view hides inconsistent tenant-level access decisions and lifecycle controls.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/08/2026 3:33 pm
Centralised SaaS governance reduces operational noise, but it does not remove tenant accountability. MSPs still have to answer for access decisions at the client boundary, where business context and entitlement rules differ. A single console can help coordinate work, yet it cannot replace per-tenant governance discipline. The practitioner takeaway is that centralisation should be treated as an operating model, not as proof of control.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
A: IT teams should start with the highest-volume repetitive tasks that consume the most staff time, then automate in a sequence that preserves control and visibility. Provisioning, user onboarding and offboarding, license tracking, compliance checks, and backup routines are common early wins. The right approach is to reduce manual toil first, then expand automation where security, accuracy, and scale can be maintained.
👉 Read our full editorial: MSP SaaS identity governance at scale: what Josys changes