QCSB Current Terminology, Non-Public Features, and Support Checklist
This article provides current 1.01.08 terminology and a support checklist; it explicitly separates real customer workflows from schema-ready/internal concepts such as Compare/Reconcile, baskets, generated packages/artifacts and other tables that are not current standalone UI features.
Use these current terms
| Term | Meaning |
|---|---|
| Storage Connection | Administrator-created reusable provider + exact root. |
| Workspace | Administrator-controlled frontend publication boundary. |
| My Private Storage | Max/All Access user-owned private remote-storage workspace. |
| Recovery protection | Safety copy created/verified before destructive actions. |
| Recovery Vault | Management surface for protected items; distinct from protection itself. |
| Effective tier | Capabilities QCSB may use now after Base tier, All Access, or active Preview is resolved. |
| Authorized Domains | Current keyless paid-entitlement control. |
Do not document dormant/internal schema as current UI
Tables/capability keys related to Compare/Reconcile, package/export artifacts, baskets, or other internal/future-ready concepts do not prove a customer workflow exists. Official documentation should follow the current 1.01.08 source/UI only.
Support checklist
- Version: installed QCSB version and Joomla/PHP versions.
- Entitlement: Base tier, Effective tier, verification/domain state, and whether Entitlement Revalidation is healthy.
- Provider context: provider type and whether Test Connection succeeds; identify the intended exact root without publishing unrestricted private paths.
- Workspace context: affected Workspace, Joomla group/role, connection override, and whether the issue reproduces with a normal account rather than only Super User.
- Operation: the exact action attempted, source/destination where relevant, conflict policy, and Transfer/Recovery state.
- Automation: affected Scheduled Task, canonical cadence, last execution/exit state, and whether server cron or Lazy Scheduler is running it.
- Safe evidence: sanitized QCSB error text and screenshots with passwords, OAuth secrets/tokens, private keys/passphrases, and legacy keys removed.
Troubleshooting
- Keep passwords, OAuth secrets/tokens, private keys, and unrestricted private paths out of public screenshots and support posts.
Community Discussion
For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.