Provider Operating Models

Any action exposed in the SHA GUI is customer-operable, subject to RBAC, edition, readiness gates, and provider access controls.

SCA changes who may be allowed to act across customer or tenant environments. It does not replace SHA as the hub for protection, recovery, EBA, SNA, snagent, controller, reporting, and health workflows.

In a standalone deployment, the customer operates SHA directly. Customer administrators run deployment, protection, recovery, maintenance, and update workflows where they are exposed in the GUI.

Partner or support assistance is optional help, not the default owner of normal GUI operations.

In an MSP-managed deployment, the customer SHA is connected to an MSP SCA for telemetry and access-controlled remote operation. Enrollment into SCA can be customer-led or MSP-led depending on the relationship.

MSP actions are delegated actions that the customer has allowed under the agreed operating model. Customer-visible SHA GUI actions remain customer-operable unless the customer has chosen to delegate them.

In a CSP-provisioned deployment, the CSP uses SCA as the provider platform layer for billing, API access, provisioning, and license management. Tenant SHA capacity is CSP-provisioned and enrolled through provider automation.

Tenant access is provider-defined: direct SHA GUI access, selected SHA capabilities, API access, or workflows exposed only through the provider's own platform. The CSP owns tenant provisioning and decides what operational surface each tenant receives.