Understand QCBM Plans, Feature Access, and Locked Controls

This topic is part of the QC Backup Manager setup and reference documentation for Joomla administrators.

This guide focuses on Basic vs Pro vs Max/All Access capability boundaries; disabled previews; saved data preserved after downgrade; current entitlement is authoritative. The feature context for this article is All plans. Use the current QCBM 1.5.13 interface and the site’s actual Status information as the authority when a saved setting or entitlement differs from an older workflow.

Before You Begin

Work from the current QCBM Status and Settings screens so the instructions reflect the installation's actual entitlement and health. Do not expose Recovery PINs, legacy keys, provider secrets, or private tokens in public screenshots or community posts.

Basic vs Pro vs Max/All Access capability boundaries

QCBM exposes a tiered feature model. Basic covers the core manual backup, verification, Recovery Package, and recovery workflow; Pro adds automation and off-site capabilities; Max/All Access unlocks the broadest feature set, including advanced storage workflows such as File Valet and QCBM Receiver where documented.

Use the current Status entitlement as the authority. A feature list is useful for planning, but the installation's effective tier determines which action is available now.

Disabled previews

QCBM can leave higher-tier controls visible but disabled so administrators can understand the feature without being allowed to run it. A disabled preview is not necessarily an error; check the entitlement or permission message attached to the control.

Saved data preserved after downgrade

When the effective tier drops, QCBM is designed to preserve saved Profiles, destinations, history, templates, and other configuration rather than deleting data simply because an action becomes locked.

Current entitlement is authoritative

The Status view's current entitlement and effective tier are the operational authority for the installed site. Do not use an old invoice, legacy key, cached screenshot, or historical preview state to infer what the installation can use now.

How This Fits into Day-to-Day QCBM Administration

Understand QCBM Plans, Feature Access, and Locked Controls is part of the administrative foundation for QCBM rather than an isolated setting. Entitlement, Joomla ACL, extension health, and recovery readiness influence which controls an administrator can use and what QCBM can safely automate.

When documenting or handing off the site, record the current domain, QCBM version, effective tier, and the location of recovery documentation. That lets another administrator distinguish an account/access problem from an actual backup-engine problem without experimenting on production data.

What to Keep for Future Troubleshooting

  • The exact Status message and effective tier.
  • The QCBM version and Joomla/PHP versions.
  • The installation UUID and current domain when they are relevant to entitlement or support.
  • The time of the last successful backup and location of a verified Recovery Package.
  • Any change you made immediately before the condition appeared.

Confirm the Site Still Has a Usable Recovery Path

Administrative changes made while following Understand QCBM Plans, Feature Access, and Locked Controls should never leave the site's backup status ambiguous. Before moving on, confirm QCBM still shows a healthy storage/recovery state and that at least one recent verified Recovery Package exists outside the server.

That checkpoint gives you a safe fallback if a later entitlement, update, permission, or configuration change produces an unexpected result.

Verify the Result

After making the change, return to QCBM Status or the owning screen and confirm the expected state is shown without a readiness warning. If the result affects paid access, confirm both the base and effective tier rather than judging only by whether a button is enabled.

Common Mistakes to Avoid

  • Treating an installation problem, entitlement problem, and Joomla ACL problem as the same issue.
  • Changing several unrelated settings before reading the current Status message.
  • Sharing credentials or recovery secrets while asking for public help.
  • Relying on old key-based instructions when the current build uses Authorized Domains.

Operational Best Practice

Keep a short operational record of the site's domain, QCBM version, effective tier, storage state, and recovery location. That makes later troubleshooting and disaster recovery faster.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.