Configure Users Shown in the Frontend User Manager

The Max/All Access Frontend User Manager uses Users shown in Frontend User Manager as its source-group filter. This setting controls which existing Joomla users are candidates to appear in delegated search results; it does not by itself make those users editable.

Protected users, excluded user IDs, the logged-in manager exclusion, and configured admin-recipient exclusion can still remove matching users from the result set.

Choose the Source Groups

  1. Open QCFUM Administrator and select Settings.
  2. Find Frontend User Manager Settings.
  3. In Users shown in Frontend User Manager, select the Joomla groups whose members should be discoverable by delegated managers.
  4. Save the settings.
  5. Test the Users tab with a non-Super-User manager account.

Source Groups Use Joomla Inheritance

The 2.0.4 query treats a configured source group as an ancestor rule. A user directly assigned to a descendant group can therefore appear when that descendant sits under a selected source group in Joomla’s nested group tree. This matches Joomla authorization semantics rather than limiting visibility to exact direct-group IDs.

Visibility Is Not Editability

A user can match the source-group filter and appear in results while still being view-only. The separate Users frontend managers may change setting controls editability. QCFUM requires the target to satisfy both source and editable rules before a sensitive change is allowed.

Protection Filters Still Win

  • Users in protected/administrative groups are excluded.
  • Explicitly excluded user IDs are excluded.
  • The current frontend manager can be excluded from their own results.
  • Configured admin-notification recipients can be excluded by email.
  • Server-side target protection is rechecked when an action is submitted.

Design the Source Set Deliberately

Use the narrowest source groups that represent the population staff actually need to find. If you select a high-level parent group, remember that descendant memberships can be included. Keep visibility broader than editability only when there is a real operational reason for staff to see view-only users.

Verify the Result

Search for one expected visible member, one member of a descendant group, one intentionally view-only user, and one protected user. This four-target test quickly shows whether source inheritance and protection rules match your intended delegation model.

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.