Assess managed SaaS capabilities
Overview
Section titled “Overview”Zbix CRM includes organization-scoped data and a bounded SaaS entitlement adapter. These foundations are distinct from a complete managed subscription service. A self-hosted CRM running in the cloud does not automatically provide automated tenant onboarding, centralized billing, high availability or certified tenant recovery.
Purpose
Section titled “Purpose”Classify existing capabilities accurately when evaluating a managed-service requirement or preparing an enterprise architecture review.
Prerequisites
Section titled “Prerequisites”-
An identified managed-service use case and intended tenant-isolation model.
-
Access to the release-specific capability evidence and operational requirements.
-
Separate owners for entitlement authority, provisioning, billing, monitoring and recovery.
Procedure
Section titled “Procedure”-
Identify which responsibilities belong to the CRM application and which would require a managed-service control plane. Record the chosen tenancy and recovery boundaries before onboarding customers.
-
Classify organization-scoped records and authorization as implemented application controls. Validate their behavior for the actual service design; do not infer shared-platform operational isolation from an organization field alone.
-
Classify the SaaS entitlement cache and update adapter as partially integrated. It accepts versioned authority updates, maintains tenant/organization binding and fails licensed writes closed after the configured staleness window.
-
Keep online subscription authority, payment processing and customer billing integration separate. The reviewed central license manager does not provide the production online subscription/revocation service needed to complete that path.
-
Classify provider recovery as a restricted handoff contract. The ordinary worker does not execute managed database snapshots or point-in-time recovery. Dedicated logical-instance assumptions apply; pooled-tenant recovery is not certified.
-
Require separate evidence for automated tenant provisioning, centralized authentication, global monitoring, availability/scaling, tenant-specific recovery and coordinated service upgrades. Mark these as not established by the reviewed release rather than claiming they are ready.
-
Approve a managed-service offer only after its missing implementation and operational qualifications are completed. Keep proposed future architecture separate from current product operating instructions.
Expected result
Section titled “Expected result”The architecture review distinguishes implemented CRM controls, partially integrated SaaS support and service capabilities that remain unqualified or not established.
Fields and controls
Section titled “Fields and controls”| Field or control | Rule |
|---|---|
| Organization-scoped CRM data and permissions | Implemented; validate the intended tenancy design separately. |
| Cached SaaS entitlement adapter | Partially implemented integration; isolated evidence, not a completed production subscription authority. |
| Online subscriptions and payment billing | Not supported as a completed central integration in the reviewed release. |
| Provider snapshot and PITR execution | Not supported by the ordinary CRM worker; restricted handoff contracts only. |
| Pooled-tenant recovery | Not production-qualified. |
| Managed provisioning, centralized SSO and global control plane | Not established by the reviewed release evidence. |
| HA, service scaling and managed upgrade orchestration | Not established; require separate architecture and qualification. |
Important notes
Section titled “Important notes”-
Implemented code is not equivalent to production qualification. The entitlement adapter has isolated integration evidence but no completed online subscription/billing authority in the reviewed release.
-
Cached entitlement freshness is bounded; an unreachable authority does not imply unlimited licensed operation.
-
A tenant administrator does not gain provider recovery authority merely by administering CRM records.
-
No managed-service availability guarantee, security certification or production RPO/RTO is established by this documentation.
Troubleshooting
Section titled “Troubleshooting”-
If licensed writes fail in SaaS mode, have the service operator review entitlement freshness, version and authority synchronization rather than changing user roles indiscriminately.
-
If recovery is queued as a provider handoff, confirm the connected authorized recovery process and do not present it as an executed restore.
-
Escalate commercial or architecture claims that depend on unverified control-plane capabilities to the service owner before customer commitment.
Related articles
Section titled “Related articles”Search the guides or talk to the ZBIX team.
Software products, application engineering and IT services from Zbix Technologies.
Visit our company website ↗