Use Approval with Direct User Creation

Explain blocking/pending behavior when direct creation requires approval and how the Approval Queue activates or rejects the onboarding request.

This guide follows the accepted QC Frontend User Manager 2.0.4 implementation and applies to Pro+; administrator and reviewer. 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

Use the unified QCFUM Dashboard rather than creating new legacy-route menu items.
Select only approved Profiles/Invite Packs and confirm the recipient email address.
Remember that generated temporary passwords and secure invitation tokens are not displayed as ordinary frontend manager data.

Step-by-Step Workflow

Open the unified QCFUM Dashboard and choose Create User.
Choose an approved User Type Profile and enter the new person’s required identity/contact information.
Add optional username, approval, or temporary-access settings only when the current workflow permits them.
Review the destination groups inherited from the Profile; do not attempt to assign groups outside the approved QCFUM configuration.
Submit the creation request and read the resulting workflow state instead of assuming every request activates immediately.
Confirm the new account in Recent Users/Tracker and verify the user received the expected private credential/welcome message.

Durable Approval Model

Approval is a stored workflow decision, not merely a hidden frontend button.
The reviewer must still have permission when acting on the pending request.
The protected action is revalidated at approval time so changed groups, target protections, or entitlement cannot be bypassed by an old request.
Downgrade or entitlement change does not justify silently deleting durable pending security decisions; availability and final authorization remain current-state dependent.

Blocking/pending behavior when direct creation requires approval and how

Explain blocking/pending behavior when direct creation requires approval and how the Approval Queue activates or rejects the onboarding request. 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 Use Approval with Direct User Creation, 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.

Current QCFUM behavior

current QCFUM behavior. 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.

Production verification

production verification. 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

Direct creation and Invite Links are the two core onboarding paths. Both create or prepare normal Joomla accounts while preserving server-side authorization and audit context.

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

Assuming an old pending approval guarantees the action can still run after groups, protections, or entitlement change.
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.