Understand QCSB Sign-In, Access Denied, and Workspace Configuration States
This article explains the frontend messages for signed-out users, users outside allowed Joomla groups, disabled/unavailable Workspaces, missing menu Workspace IDs, and locations they cannot browse.
Common frontend states
| State | What to check |
|---|---|
| Sign in required | The menu/view requires an authenticated user and no usable signed-in session is present. |
| Access denied | The user can reach the route but Joomla/QCSB authorization does not allow the Workspace/private action. |
| Workspace unavailable/disabled | The selected Workspace does not exist in a usable enabled state. |
| No usable storage | The Workspace may exist but its connections are disabled/unavailable or the user has no permitted location. |
| Provider/action unavailable | The Workspace loads, but a specific operation is hidden/disabled because of role, override, plan, provider state, or item state. |
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.