Delete Files or Folders Safely with Recovery Protection
This article shows how to delete selected items only after QCSB creates verified Recovery protection; if protection cannot be created, the destructive action is blocked rather than proceeding unsafely.
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.
- 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 to do it
- Select the permitted file(s) or folder(s).
- Click Delete and review the confirmation.
- QCSB attempts to create and verify a protected Recovery copy for each destructive item before removing provider content.
- If recovery protection cannot be created, QCSB blocks the destructive action for that item rather than proceeding unprotected.
- Review the operation result. When Recovery Vault management is available, confirm the protected item is present and carries the expected retention information.
Verify the result
- The provider reflects the intended final file/folder state.
- The QCSB result reaches the expected outcome without an unresolved sanitized error.
- The required Recovery protection exists before destructive provider content is removed.
Important limits and mistakes to avoid
- Do not bypass failed recovery protection to force a destructive action. The block is intentional safety behavior.
Troubleshooting
- If a file action fails, retry with one small test item and read Transfer Details or the operation toast before changing global settings.
- If a destructive action is blocked because recovery protection failed, repair recovery storage/capacity first; do not bypass the protection boundary.
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.