Concept
CSP-Provisioned Tenant SHA
How CSP-led provisioning and tenant access work through SCA and SHA.
Relationship
In a CSP model, the provider leads tenant SHA provisioning and controls how the tenant consumes Sendense capabilities.
CSP operating model
The CSP provisions tenant SHA capacity through SCA and decides how each tenant consumes Sendense: SHA GUI access, selected capabilities, API access, or only provider-platform workflows.
Provider-led automation
CSP enrollment is provider-led and intended to be automated as part of tenant provisioning through SCA-led workflows.
Tenant access is a provider choice
A tenant might receive SHA GUI access, selected SHA capabilities, API access, or only workflows exposed through the CSP's own platform.
Provider Platform Layer
The CSP uses SCA as the provider platform layer for multi-tenant billing, API access, provisioning, and license management. Each tenant SHA remains the hub appliance for that tenant's deployment.
Provider-Led Provisioning
Tenant SHA capacity is CSP-provisioned and enrolled through provider automation as part of tenant provisioning. The CSP owns tenant provisioning; customer-led SHA enrollment is not the normal tenant path.
Tenant Access
Tenant access is provider-defined. A tenant might receive direct SHA GUI access, selected SHA capabilities, API access, or only workflows exposed through the CSP's own platform.
API-only or provider-platform-only access is a valid CSP model. It is not a product limitation; it is an access model chosen by the CSP.
CSP Versus MSP
CSP provider-controlled tenancy is not the same as MSP delegated access. In the MSP model the customer operates SHA and delegates agreed actions; in the CSP model the provider provisions tenant capacity and defines the tenant's operational surface.
Related Docs