Install or Upgrade QC Frontend User Manager and Verify Version 2.0.4

Use the outer package, install over the existing version, verify component and task plugin registration, then confirm the installed version and basic health in Status. Do not recommend uninstalling before normal upgrades.

This guide follows the accepted QC Frontend User Manager 2.0.4 implementation and applies to All plans; administrator. QCFUM delegates selected Joomla user-onboarding and management workflows without making frontend staff Joomla backend administrators. When older manuals or walkthrough wording differs from the current source or accepted keyless-entitlement behavior, the current implementation takes precedence.

Before You Begin

Take a current Joomla/site backup before installation, upgrade, or structural changes.
Confirm Administrator access and permission to install extensions and inspect Scheduled Tasks.
Record the current QCFUM version and Base/Effective tier before entitlement or task changes.

Step-by-Step Workflow

Create a current site/database backup and record the existing QCFUM version.
Install the current outer QCFUM package over the existing installation through Joomla; do not uninstall first for a normal update.
Confirm the component and QCFUM Scheduled Tasks plugin are installed/enabled.
Open QCFUM → Status and verify version 2.0.4, entitlement, installation identity, update state, and task health.
Open the unified frontend Dashboard with a safe delegated test account and perform a basic smoke test.

Server-Side Safeguards

Joomla menu access, QCFUM ACL, product entitlement, and target-specific authorization are separate gates.
Super Users and equivalent protected administrative accounts remain protected server-side.
Visibility does not automatically imply editability; a user may be shown but intentionally view-only.
Allowed destination groups are constrained independently from the groups a target user currently has.
Bulk actions re-authorize each selected target server-side; the UI selection is never the security boundary.
Password resets are delivered privately; frontend managers do not receive the generated password.
The QCFUM MFA Required value is an administrative flag only, not Joomla MFA enforcement.

The outer package, install over the existing version, verify

Use the outer package, install over the existing version, verify component and task plugin registration, then confirm the installed version and basic health in Status. In QCFUM 2.0.4, this must be evaluated together with the current Effective tier, the Joomla/QCFUM permissions of the acting account, and target/workflow safeguards. QCFUM is designed to fail closed around protected users and sensitive actions rather than trusting the presence of a frontend button as authorization.

For Install or Upgrade QC Frontend User Manager and Verify Version 2.0.4, test the exact workflow with a safe non-administrator account and a deliberately chosen target. QCFUM’s frontend presentation is not the authorization boundary: a control can be visible while the server still refuses an unsafe target, an unavailable tier, an invalid workflow state, or a group change that violates administrator-defined safeguards.

Do not recommend uninstalling before normal upgrades

Do not recommend uninstalling before normal upgrades. In QCFUM 2.0.4, this must be evaluated together with the current Effective tier, the Joomla/QCFUM permissions of the acting account, and target/workflow safeguards. QCFUM is designed to fail closed around protected users and sensitive actions rather than trusting the presence of a frontend button as authorization.

How This Fits into QCFUM

This category establishes the installation, entitlement, update, and administrative foundation. It should be completed before delegating frontend onboarding to staff.

A reliable QCFUM configuration keeps Joomla authoritative for real user accounts while QCFUM owns the delegated workflow, attribution, approval, automation, and safety rules around those accounts. This separation matters during upgrades and downgrades: preserving QCFUM records does not mean every preserved premium feature remains usable at a lower Effective tier.

Security and Data-Protection Notes

Use least privilege for menu access and QCFUM ACL; grant staff only the actions required for their role.
Never share passwords, invite tokens, API credentials, or private account data in screenshots, support requests, or custom email content.
Treat Super Users and equivalent administrative-capability accounts as protected even when a UI configuration appears permissive.
Verify destructive or access-changing actions with a safe test account before enabling them for production staff.
Remember that uninstall/reinstall is not a supported method for wiping QCFUM business data or resetting entitlement/preview history.

Verify the Result

The resulting Joomla user/group state matches the intended QCFUM workflow.
A protected or out-of-scope user remains protected when tested with the delegated staff account.
Reload the real frontend/Administrator view rather than relying only on a saved form message.
Repeat the critical test using the exact non-Super-User group that will operate the workflow.

Common Mistakes to Avoid

Testing only as Super User instead of the actual delegated staff group.
Changing multiple security/workflow settings at once during troubleshooting, making the real cause difficult to identify.

Troubleshooting

If a control or tab is missing, check Effective tier, QCFUM ACL, menu access, and feature configuration before assuming installation damage.
If a user cannot be selected or changed, check protected groups/IDs, core administrative protection, visibility/editability rules, destination-group rules, and the delegated manager’s exact permissions.
If onboarding stalls, inspect the stored workflow status (invite, approval, import, temporary access) rather than deleting the record and starting over immediately.
If automation does not run, verify Joomla Scheduled Tasks and distinguish the hourly Entitlement Revalidation task from the separately configured Scheduled Automation task.
If email does not arrive, verify Joomla mail transport independently, then inspect QCFUM template publication, recipient/address, queue state, and retry eligibility.

Operational Best Practice

Keep onboarding definitions simple enough that staff can select the correct Profile/Pack without guessing. Test every delegated workflow with the real staff Joomla group, keep entitlement/tasks healthy, and preserve an Administrator recovery path. When changing user-management safeguards, verify both a target that should be allowed and a protected target that must still be refused.

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.