Protect Specific Joomla User IDs from Frontend Management
QCFUM 2.0.4 lets a Max or All Access administrator exclude individual Joomla user IDs from the Frontend User Manager. This is useful for special accounts that should never be delegated even when their Joomla groups would otherwise make them visible or editable.
Where the Setting Lives
Open Components > QC Frontend User Manager > Settings and find Frontend User Manager Settings. The field is labeled User IDs hidden from all frontend changes.
Enter Joomla user IDs as a comma-separated list, for example 123, 456. Use Joomla’s Users screen to verify each ID before saving.
What the Exclusion Actually Does
The exclusion is enforced by QCFUM’s server-side managed-user protection check. If the target user ID is in the saved exclusion list, QCFUM treats that account as protected even if the account also belongs to a visible and editable group.
- The account is removed from normal delegated management results.
- Frontend User Manager actions recheck the target before applying changes.
- The exclusion does not delete, block, or modify the Joomla user itself.
- Other automatic protections, such as administrative-capability protection, still apply independently.
When to Use Specific User IDs
Use the ID list for exceptions that are difficult to express safely with group rules: service identities, integration accounts, executive accounts, recovery accounts, or any other specific Joomla user that should remain outside delegated management.
For whole classes of accounts, prefer protected-group configuration instead of maintaining a long user-ID list.
Safe Configuration Procedure
- Identify the exact Joomla user and confirm its numeric user ID.
- Add that ID to User IDs hidden from all frontend changes.
- Save QCFUM Settings.
- Sign in with the real non-Super-User staff account that uses the Frontend User Manager.
- Confirm the protected account no longer appears as a manageable target.
- Also verify that an ordinary allowed account still appears and can be changed as intended.
Do Not Use the List as Your Only Safeguard
Specific IDs are one layer, not the entire security model. Keep menu access, QCFUM frontend ACL, visible groups, editable groups, allowed target groups, protected groups, current-user exclusion, and administrative-account protection configured correctly as well.
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.