Test a QCSB Storage Connection Before Putting It in a Workspace

This article shows how to use the connection test workflow to validate credentials, provider reachability, root access, and provider-specific trust/OAuth state before relying on a connection in production.

How to do it

  1. Open Storage Connections and create or edit the connection you want to verify.
  2. Confirm the provider, credentials, exact root, and subdirectory setting are correct for the intended storage area.
  3. Click Test Connection. The test validates provider reachability and access to the configured root without changing the provider type.
  4. For Google Drive or OneDrive, complete the account connection first; an OAuth provider cannot pass a meaningful root test until authorization is active.
  5. Do not add the connection to a production Workspace until the test succeeds and the displayed root is the intended root.

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.
  • 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.
  • 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.