Understand Storage Connections, Workspaces, Panels, Transfers, and Recovery Protection
This article introduces the current QCSB object model and how an exact provider root becomes a Storage Connection, how Workspaces publish selected connections, how panels expose them, how operations become durable jobs, and how destructive actions are protected first.
What you need to know
- Basic includes Local storage and the first active Workspace. Pro adds FTP/SFTP, multiple Workspaces, advanced permissions, and background continuation. Max/All Access adds Google Drive, OneDrive, Private Connections, Recovery Vault management, and bulk operations.
- A plan gate decides whether a feature exists at the current Effective tier. Joomla access and QCSB permission rules separately decide whether a particular user may use that feature.
- QCSB uses durable jobs but follows an immediate-first model: the request attempts ordinary work immediately, and only unfinished work remains for continuation.
- Pro/Max/All Access can use the 5-minute Transfer Continuation task. The worker rechecks the original user’s current authority before contacting a provider.
- Recovery protection is a safety boundary for destructive operations and is separate from Max/All Access Recovery Vault management. QCSB may create protected copies even when the current user cannot open the management UI.
- Delete, replace/overwrite, and destructive move are blocked when the required protected copy cannot be created and verified.
How the objects relate
| Object | Purpose |
|---|---|
| Storage Connection | One administrator-created provider plus one exact root and its stored credentials/settings. |
| Workspace | Publishes selected shared connections to selected Joomla groups with a role and optional per-connection overrides. |
| Panel / storage view | The frontend view of one currently authorized location/connection. Layout state never expands the root or permission boundary. |
| Transfer job | Durable record for copy/move work that may complete immediately or continue later when Pro+ background continuation is available. |
| Recovery protection | Verified protected copy created before QCSB removes or overwrites provider content during destructive operations. |
| Recovery Vault | Max/All Access management UI for protected records; it is not the same thing as the underlying safety protection. |
Verify the result
- The durable job reaches the expected terminal state: completed, completed with warnings, failed, or cancelled.
- Successful items remain successful; failed/retried items report their own sanitized outcome.
- For a Move, the source is removed only after the destination is verified and the source has required Recovery protection.
Important limits and mistakes to avoid
- Never broaden a connection root merely to work around a permission or provider error; fix the actual root/credential/hosting problem.
- Do not bypass failed recovery protection to force a destructive action. The block is intentional safety behavior.
- A successful Super User test does not prove a normal Joomla group has correct Workspace access. Test with the real role.
Troubleshooting
- If the provider is unreachable, test the connection in Administrator before troubleshooting the Workspace UI.
- If an action is missing/denied, check Joomla menu access, Workspace allowed group, Workspace role, custom denies, connection override, and plan gate separately.
- If a destructive action is blocked because recovery protection failed, repair recovery storage/capacity first; do not bypass the protection boundary.
- 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.