Delete a Storage Connection Safely
This article explains the requirement to remove a connection from all Workspaces before deletion, what QCSB removes locally, and why deleting a QCSB connection does not delete the actual provider files.
How to do it
- Open Workspaces and remove the connection from every Workspace that currently uses it.
- Confirm there is no active transfer that still depends on the connection; QCSB blocks deletion while active transfer items remain.
- Return to Storage Connections and click Delete on the connection card.
- Confirm the deletion prompt. QCSB removes the local connection/secret relationship but does not delete files stored at the provider.
- Historical transfer/audit references are preserved through soft references rather than being rewritten as if the connection never existed.
Verify the result
- Test Connection succeeds.
- The displayed/usable root is exactly the intended root and no parent folder is reachable.
- A normal authorized user can perform only the operations intended for that connection/Workspace role.
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.
Troubleshooting
- If the provider is unreachable, test the connection in Administrator before troubleshooting the Workspace UI.
- If a file action fails, retry with one small test item and read Transfer Details or the operation toast before changing global settings.
- 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.