Cross-tenant context
Cross-Tenant Search
Find user cases and rules across actually managed tenants and return to the right customer context.
MSPs and service providers
Support more tenants. Keep customer context visible.
Authorized cross-tenant search, roles and delegation, and policy baseline and drift bring managed customer environments into a consistent operating view.
Delegation
Roles and Delegation
Keep tenant binding, permission and service responsibility transparent for the operator.
Service review
Policy Baseline and Drift
Compare an agreed reference state with customer-specific differences and prepare a conscious review.
Diagnosis
Unified Support Center
Use the same structured user, policy, tunnel and available experience context across customers.
In the MSP workflow
Repeatable diagnosis creates capacity, not more open portals.
Each case begins in the correct managed tenant, with the appropriate role and a clearly visible customer responsibility.
Capture user cases consistently
Apply the same first-line diagnostic method without giving the service desk unnecessary broad rights.
Go deeper with customer context
See user, policy, tunnel and available experience details without restarting the information search.
Prioritize patterns and differences
Use cross-tenant context and policy drift as a reviewable service input.
Standardize without losing specifics
Keep tenant, role, contract context and customer-specific exceptions visible.
Scalable service delivery
Growth becomes manageable through repeatable workflows.
CentaurNexus connects technical operations across authorized tenants with an understandable service context.
Select customer context
Start in the correct managed tenant with the appropriate role.
Process the case consistently
Follow a repeatable diagnosis, approval and handover path that retains tenant context.
Make service work visible
Use status, drift and recurring patterns as input for service reviews and priorities.
Roles and delegation
Scaling begins with clear tenant and role context.
While a case is being processed, the interface keeps the customer, tenant, acting role and responsibility visible. MSP access remains restricted to the tenants the MSP actually manages.
- Tenant binding stays visible in the workflow.
- Permissions follow the delegated customer responsibility.
- Sensitive actions remain governed by the customer tenant policy.
Concrete MSP capabilities
Three capabilities support multi-tenant operations.
The platform focuses on repeatable service workflows and explicit customer accountability.
Cross-Tenant Search
Find user cases and rules across managed tenants.
Roles and Delegation
Assign tenant, permission and responsibility.
Policy Baseline and Drift
Use reference context and customer differences for review.
Controlled implementation
Move reviewed individual changes into the tenant-specific approval path.
Service with customer context
Standards work when responsibility stays visible.
A shared operating model helps teams resolve recurring cases faster while keeping customers and tenants distinct.
Next step
Review your service model
Bring one recurring operating situation. We will map the roles, required context and appropriate demo path.
Frequently asked questions
Scaling Zscaler services across managed tenants.
How does CentaurNexus support multiple Zscaler tenants?
Cross-tenant search, roles and delegation, and policy baseline and drift connect repeatable service workflows with visible customer context.
Can the MSP help desk work without full admin rights?
Yes. User Support Center provides the role-approved first finding. Complex cases can be handed to second level or administration with structured context.
How is customer responsibility kept separate?
Tenant, role and delegation are part of the operational context. Access remains limited to the tenants the MSP actually manages.
How do service improvements become visible?
Policy drift, recurring findings and cross-tenant patterns provide reviewable inputs for prioritization and service reviews.