Configure Groups Always Hidden or Protected from Frontend Management
Max and All Access sites can add ordinary Joomla groups to QCFUM’s protected set so members of those groups are hidden from delegated frontend management and cannot be changed through the Frontend User Manager.
This manual list supplements QCFUM’s automatic protection for groups and users with administrative/backend capabilities.
Open the Frontend User Manager Settings
- Open Components > QC Frontend User Manager.
- Open the Settings tab.
- Find Frontend User Manager Settings.
- Under Groups always hidden/protected, select every Joomla group that delegated staff must never manage.
- Save the settings and test with the real delegated staff group.
What the Protected-Group Setting Does
QCFUM stores the selected group IDs and removes matching users from Frontend User Manager results. Sensitive User Manager actions also recheck the target before changing it, so protection is not merely a display filter.
Joomla Group Inheritance Applies
QCFUM evaluates authorized membership through Joomla’s nested group hierarchy. If you protect a parent group, a user directly assigned to a descendant group can also match that protected ancestor. This is important when your site uses custom child groups under Manager, Administrator, or other sensitive branches.
Administrative Capability Protection Cannot Be Removed Here
QCFUM automatically adds groups that grant core.admin, core.login.admin, or core.manage to its protected set. If an administrator accidentally removes one of those groups from the manual list, the capability-based protection still applies.
Good Candidates for Manual Protection
- Backend-management or site-operations groups.
- Service/integration accounts grouped together for operational reasons.
- Finance, ownership, or other high-risk groups that frontend staff should never modify.
- Any custom parent group whose descendants should also be outside delegated management.
Verify Before Production
Sign in as a non-Super-User frontend manager. Search for one ordinary user that should appear and one user in a protected group. The ordinary user should follow your source/editable rules; the protected user should not become a manageable target even if that user would otherwise match a source group.
Community Discussion
Want to compare Joomla user-management safeguards, share practical QCFUM configuration ideas, or discuss how other administrators delegate frontend workflows? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.