Understand QCSB Workspaces as the Frontend Publication Boundary

This article explains that Storage Connections do not automatically become frontend-accessible: a Workspace selects which shared connections are published, which Joomla users may enter, and what operations they may perform.

What a Workspace controls

• Which administrator-created Storage Connections are available.
• Which Joomla groups are allowed.
• The preset/custom role for each allowed group.
• Connection-specific overrides such as Use Workspace Role or No Access.
• The frontend publication selected by the Joomla File Workspace menu item.

What a Workspace does not do

A Workspace does not move or duplicate provider files. The same Storage Connection can be reused in several Workspaces with different groups/roles. Disabling or deleting the Workspace changes publication/access, not the underlying provider content.

Verify the result

• An allowed normal account can open the intended Workspace.
• An account outside the allowed rules cannot use the Workspace/action.
• Connection overrides and source/destination permissions behave exactly as configured.

Important limits and mistakes to avoid

• A successful Super User test does not prove a normal Joomla group has correct Workspace access. Test with the real role.

Troubleshooting

• If an action is missing/denied, check Joomla menu access, Workspace allowed group, Workspace role, custom denies, connection override, and plan gate separately.

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.