Troubleshoot a User Who Does Not Appear or Cannot Be Managed

QCFUM deliberately separates visibility, editability, and allowed actions for existing Joomla users. A person can be absent entirely, visible as View only, or editable but still unable to perform a particular action.

Diagnose those layers in order instead of widening permissions until the account appears.

Confirm the Frontend User Manager Itself Is Available

Existing-user management requires Max / All Access, an active product entitlement, an authenticated user, Enable Frontend User Manager, and access to the Users tab. If that feature is unavailable, individual target settings are not the first problem.

Why a User Does Not Appear

The target must belong—through Joomla group inheritance—to one of the configured Users shown in Frontend User Manager groups. QCFUM then removes explicit excluded user IDs, the current manager when that protection is enabled, configured administrator-recipient emails when enabled, and accounts in protected groups. Accounts with core.admin, core.login.admin, or core.manage capability are also protected server-side.

Why a Visible User Says View Only

Visibility comes from the source-group list; editability additionally requires membership in one of Users frontend managers may change. If the account passes visibility but not the editable-group test, QCFUM can show it as View only. Protected accounts are removed/refused rather than intentionally exposed as editable.

Why One Action Is Still Missing or Refused

Identity edit, password reset, require-reset, status change, group change, deletion, MFA flag, and bulk actions each have separate administrator toggles. Group changes also require every requested direct target group to be in the safe allowed-target set and not protected. Deletion has its own configured behavior and optional approval path.

Retest with the Exact Staff Account

Use the actual non-admin Joomla group assigned to the staff member. Super Users bypass many ACL checks and are poor permission-test accounts. Search the target by name/email, expand the row, note View only/editable state, then test only the intended action.

Community Discussion

Want to compare Joomla user-management 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.