WebBlocks Support

Documented package version: 0.3.3. WebBlocks CMS ^1.75.0; PHP >=8.4.

Provider-independent support tickets for WebBlocks CMS. The plugin owns the Support admin menu, activation state, encrypted installation credential and ticket UI. CMS core contains no support-provider or commercial workflow.

The provider contract is documented in docs/webblocks-support-protocol-v1.md. An installation begins activation only after its administrator enters a single-use invitation code supplied by the provider. Approval is then handled by the provider operator while the CMS polls from its own Support screen; CMS users do not need a provider account.

Open Support in CMS admin and configure a compatible support provider. Enter the single-use invitation code supplied by that provider. The CMS submits the activation request and polls from the Support screen while the provider operator reviews it. No separate provider account is needed for CMS users.

After activation, use Support to create tickets, read your tickets and send replies. Access is scoped to the installation and ticket owner. The provider determines the available support entitlement.

A provider may request a system summary, recent application errors or plugin health. Review the requested categories and approve or decline before anything is collected or sent. Credentials, cookies, environment files and full logs are excluded.

webblocks-support.access permits ticket use. webblocks-support.manage permits management of the provider connection.

See the Support protocol for discovery, activation, ticket endpoints and diagnostics.