A platform administrator owns global capabilities, delegation rules, and non delegable actions across the SaaS service. A customer administrator works only inside one tenant and can manage the permissions, roles, and settings the provider has explicitly allowed. The distinction matters because delegated administration is not shared ownership. It is controlled local administration under a provider defined boundary.
How delegated administration draws the boundary between provider control and tenant control
Delegated administration is a boundary model, not a shared-control model. The platform administrator controls the service-wide delegation rules, global capabilities, and actions that remain non delegable. The customer administrator is limited to the tenant they manage and can only work within the permissions and settings the provider has intentionally exposed. That separation is what keeps local administration from becoming global authority.
The practical difference is scope. A platform administrator can define what delegation means across the SaaS environment, including which roles may be assigned and which actions stay reserved to the provider. A customer administrator may have meaningful operational authority, but only inside the tenant boundary and only for the functions the platform has allowed.
That boundary is also why delegated administration should be read as controlled delegation, not ownership transfer. The customer can administer their environment, but they do not inherit the provider’s service-level responsibilities or unrestricted access to the platform.
What each administrator can and cannot change
A platform administrator typically governs the underlying delegation model itself. That includes the architecture of admin delegation, the rules that determine who can administer what, and the exceptional actions that must remain centralized for service integrity, support, or security. When this model is well designed, it prevents tenant admins from accidentally or deliberately stepping outside their lane.
A customer administrator works in a narrower operational frame. They can usually manage users, groups, roles, policies, or tenant settings that the provider has approved for customer control. They do not get the ability to alter the provider’s global controls, service-wide security posture, or cross-tenant boundaries just because they are “an admin.”
- Platform admin, global delegation policy and reserved actions.
- Customer admin, tenant-local permissions and provider-approved settings.
- Platform admin, can change the rules of delegation.
- Customer admin, can operate only within the delegated rule set.
Why the distinction matters in SaaS operations
The distinction matters because admin labels are not interchangeable. In delegated administration, the question is not whether someone is “an administrator,” but whether they hold global service authority or bounded tenant authority. If teams blur that line, they may overestimate customer-side control, understate provider responsibility, or assume a tenant admin can remediate issues that only the platform side can change.
This is also where escalation paths become important. If a tenant admin needs an action that sits outside the customer boundary, the issue must move to the platform side rather than be worked around locally. Clear role separation reduces unsafe exceptions, prevents privilege creep, and makes audit expectations clearer for both sides. The NHI Management Group B2B CIAM and Organisation Management Guide is a useful reference for the tenant-boundary thinking behind organisation scope, tenant isolation, and delegated admin workflows.
The same principle applies when partner or provider tooling is involved. GDAP and MSP Delegated Admin Access Guide shows how least-privilege delegation depends on tightly defining which admin rights are actually transferable and which remain centrally controlled. The more precisely that boundary is defined, the less likely it is that “delegated admin” becomes a backdoor to broader control.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CSA Cloud Controls Matrix and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CSA Cloud Controls Matrix | IAM — Identity and Access Management | Delegated administration is fundamentally an IAM scope and role-boundary problem. |
| Recommendation — Define tenant-scoped and provider-scoped admin rights separately, then enforce them in the access model. | ||
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | The distinction depends on limiting customer admins to only the rights the provider delegates. |
| Recommendation — Restrict each admin role to the minimum authority needed for its scope. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Delegated administration requires formally defined access boundaries and approvals. |
| Recommendation — Document and enforce role boundaries so delegated access stays within approved limits. | ||
Practitioner Guidance
What to verify: Confirm whether the role is tenant-scoped or service-scoped before granting it. The title alone is not enough; the permission boundary and non delegable actions are what determine real authority.
Decision rule: If an action affects the service itself, cross-tenant control, or the delegation model, treat it as platform-admin territory. If it affects only one tenant and is explicitly allowed by the provider, it belongs with the customer admin.
Common mistake: Treating customer administrator as a “smaller platform administrator” leads to over-delegation and weakens the provider-defined boundary that delegated administration depends on.
Practitioner takeaway: The key test is not who can administer, but what they can administer, across which boundary, and under whose control.
Related resources from NHI Mgmt Group
- How should delegated customer administration be controlled in a B2B SaaS platform?
- How should SaaS teams implement delegated administration without giving customer admins too much power?
- What is the difference between self-service administration and safe delegated control?
- How should security teams govern customer OAuth tokens held by a platform?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org