What QC Storage Bridge Does and How the Storage Workflow Fits Together
This article explains QCSB as a Joomla-native secure file workspace spanning shared Storage Connections, published Workspaces, durable file operations, provider isolation, recovery protection, and optional private storage without pretending it is a backup, synchronization, or public-download system.
From provider to frontend
| Stage | What QCSB does |
|---|---|
| 1. Storage Connection | An administrator defines one provider and one exact root, stores the needed credentials, and tests it. |
| 2. Workspace | The administrator selects one or more shared connections and assigns Joomla groups a Workspace role/overrides. |
| 3. Joomla menu item | A File Workspace menu item publishes that Workspace to the intended Joomla access level. |
| 4. Frontend panels | Allowed users browse one or more authorized storage panels without receiving provider credentials or Joomla Administrator access. |
| 5. File operation | Upload/download/create/rename/copy/move/delete are re-authorized server-side for the current source and destination. |
| 6. Durable safety/state | Long-running work becomes a durable job; destructive work is Recovery-protected before provider content is removed. |
What QCSB does not replace
Use QC Backup Manager for complete Joomla backup/recovery. QCSB is not an automatic bidirectional sync engine, malware scanner, anonymous public-download library, or full document-management/collaboration suite. Its job is controlled file access and transfer across explicitly authorized roots.
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.