Understanding QCUL Joomla Permissions at a Glance

QCUL uses focused Joomla ACL permissions for laboratory/settings/report work and adds a stricter Super User requirement around live production push and rollback.

Current component permissions

PermissionAllows
Manage SettingsChange QC Update Laboratory settings.
Create LaboratoriesCreate a private update-testing laboratory.
Test and Manage UpdatesCreate or refresh the laboratory, test updates, and continue paused work.
View LaboratoriesView laboratory status and private access details.
Remove LaboratoriesPermanently remove the private laboratory and its temporary rollback checkpoints.
Download ReportsView and download update-test and production reports.

Production authority is stricter

Production push and production rollback require a Joomla Super User with the necessary QCUL operation permission. QCUL reloads the exact run/item/package/current state server-side before protected work; a visible button or modified form submission is not sufficient authorization.

Recommended delegation

Give support staff only the smallest permissions they need. A reviewer can receive View Laboratories and Download Reports without Remove Laboratories. Keep live production push/rollback with a small group of experienced Super Users.

Practical administration note

For Understanding QCUL Joomla Permissions at a Glance, make changes from the live Joomla administrator and verify the result in the same QCUL tab before starting laboratory work. QCUL’s streamlined 1.01.14 interface intentionally hides developer storage paths, raw batch controls, licensing fields, and retired management screens; do not look for those older controls as part of the current procedure.


Community Discussion

Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.