Configure Optional QCFUM Approval Workflows

Enable approval only for the workflows that need review: direct create, Invite Links, CSV direct, CSV Invite, frontend group changes, and frontend deletion.

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

Confirm Effective Pro/Max access before relying on CSV, approval, or temporary-access features.
Preview imports before committing them and use a small controlled test first.
Keep Scheduled Automation healthy whenever temporary access already exists, even if commercial automation is turned off.

Step-by-Step Workflow

Open Invitations in the unified QCFUM Dashboard.
Choose the appropriate Invite Pack/Profile workflow and enter the recipient information.
Review expiration, approval, landing, and email behavior inherited from the Pack.
Create/send the Invite Link and confirm the new record appears in invitation history/Tracker.
If the workflow requires approval, process it through the authorized Approval Queue before expecting a usable setup link.
Test completion with the recipient flow and confirm the resulting Joomla account/group state.

CSV Intake Reference

Item	Current behavior
Required	name, email
Optional	username, method, profile, invite_pack
Mode	Direct Create or Invite Link; a row method may override the selected default
Security	No password column; temporary passwords are generated/delivered privately when direct creation requires them
Hard upload ceiling	2 MB, plus the administrator-configured row limit

Always use Preview before committing a production import. A valid upload can still contain rows that QCFUM refuses because of duplicate identity, invalid workflow selection, unavailable Profile/Pack, group protection, or current tier/allowance limits.

Enable approval only for the workflows that need review:

Enable approval only for the workflows that need review: direct create, Invite Links, CSV direct, CSV Invite, frontend group changes, and frontend deletion. 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 Configure Optional QCFUM Approval Workflows, 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

CSV, durable approvals, and temporary-access expiration add scale and control. Security enforcement is deliberately separated from optional commercial automation.

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.
Invitation status, expiration/approval state, Pack/Profile mapping, and delivery status are consistent.
Preview/summary counts match the intended rows and no password column or unauthorized workflow slipped through.
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 inherited Joomla group visibility means QCFUM should write inherited memberships rather than direct memberships.
Skipping Preview or adding a password column to the CSV.
Treating invitation status/delivery as equivalent to a permanently reusable plaintext token.
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.