Enable the Max Frontend User Manager Safely
The Frontend User Manager lets delegated staff work with eligible existing Joomla users from the frontend. Because it can expose identity, status, password-reset, group-change, and deletion workflows, enable it only after the visibility and protection rules are deliberately configured.
The feature requires an active Max or All Access entitlement, an authenticated frontend user with qcfum.frontend.manage_users, and the Administrator setting Enable Frontend User Manager.
Configure Scope Before Enabling
| Setting | Purpose |
|---|---|
| Users shown in Frontend User Manager | Source groups whose members can appear; Joomla descendant memberships are included through inheritance logic. |
| Users frontend managers may change | Editable groups. Visible users outside this set can remain view-only. |
| Groups frontend managers may assign/remove | Safe direct-membership targets for group editing. |
| Groups always hidden/protected | Accounts in these groups are removed from frontend management. |
| User IDs hidden from all frontend changes | Explicit account-level exclusions. |
Keep the Default Safety Exclusions
By default QCFUM excludes the current frontend manager and configured administrator-notification recipients. It also automatically protects accounts/groups with core.admin, core.login.admin, or core.manage capability, including inherited authorized groups.
Enable Only the Actions You Need
Identity editing, password reset, require-reset, status change, group change, deletion, MFA administrative flag, and bulk actions are separate settings. Group change and deletion start disabled by default. Leave destructive capabilities off unless the staff role actually requires them.
Test with the Real Staff Group
- Grant the exact Joomla frontend ACL action to the intended staff group.
- Sign in as a non-Super-User account in that group.
- Verify an allowed user appears.
- Verify a view-only user cannot be changed.
- Verify a protected administrative account does not appear or cannot be acted on.
- Test each enabled action before production use.
Downgrade Preserves Configuration
If the site later drops below Max, the Frontend User Manager becomes unavailable but its saved settings remain stored. Upgrading restores the feature subject to the current entitlement and settings; preservation does not bypass current safety checks.
Community Discussion
Want to compare Joomla user-onboarding workflows, share practical QCFUM tips, or discuss how other administrators use this feature? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.