Google Drive Exact Roots and Subdirectory Boundaries

This article explains how QCSB constrains Google Drive browsing to the configured root, how provider folder identifiers are handled, and how Allow Subdirectories changes depth without allowing traversal above the root.

What you need to know

  • Each Storage Connection represents one provider and one exact root. QCSB normalizes paths and refuses navigation/operations outside that boundary.
  • Allow access to subdirectories controls depth below the root; it never exposes or infers parent directories above the root.

Apply the Drive root correctly

  1. Choose the correct provider context first: My Drive or the intended Shared Drive.
  2. Set the QCSB exact root to the folder that should be the top of this connection.
  3. Enable subdirectories only if Workspace users should enter descendants under that root.
  4. Save/connect the Google account and run Test Connection so QCSB verifies the selected Drive/root.
  5. Test from a normal Workspace account and confirm no parent Drive location is reachable. Deep navigation may use signed provider object identifiers, but those identifiers do not expand the saved 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.

Troubleshooting

  • If the provider is unreachable, test the connection in Administrator before troubleshooting the Workspace UI.
  • 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.