Why QCSB Actions Can Be Disabled or Hidden

This article explains how to interpret permission-, plan-, selection-, and destination-dependent action availability and use the supplied tooltips/messages instead of assuming a disabled control is a browser defect.

Reasons an action may not appear

• The current Workspace role does not include the permission.
• A connection-specific override narrows the role or sets No Access.
• The current Effective tier does not include the feature/provider.
• The Storage Connection or Workspace is disabled/unhealthy.
• The provider/item type does not support the operation in the current context.
• The current selection is invalid (for example, Download/Rename requires exactly one file/item).
• Recovery protection or another safety prerequisite cannot be satisfied.

Security rule

Hidden/disabled controls are only user-interface guidance. QCSB rechecks the action server-side, so manually changing a request cannot turn a denied operation into an allowed one.

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.