Configure Optional QCFUM Approval Workflows
QCFUM approval is optional, off by default, and available from Pro upward. Administrators can require review for specific onboarding and frontend-management actions instead of forcing one approval rule onto every workflow.
These switches are stored under Settings → CSV Import & Approval Settings. They do not replace Joomla/QCFUM ACL, current entitlement, protected-user rules, or Profile/Invite Pack validation.
The Six Approval Switches
| Setting | What it holds for review |
|---|---|
| Direct Create requires approval | Normal frontend Direct Create accounts. The Joomla user is created blocked/pending until reviewed. |
| Invite Links require approval | Normal Invite Link issuance. The Invite record is pending and the secure link is not sent until approval. |
| CSV direct-created users require approval | Direct rows created by CSV Import. |
| CSV Invite Links require approval | Invite rows created with CSV context; normal Invite-Link approval can also apply. |
| Frontend group changes require approval | Max/All Access Frontend User Manager group-change requests become durable approval requests instead of immediate writes. |
| Frontend deletion requires approval | Frontend user deletion is held for review; the separate deletion-behavior setting can also require approval. |
Approval Settings Are Workflow-Specific
The CSV Direct setting is checked by the CSV Direct creation path. CSV Invite creation enters the normal Invite function with CSV context, so the CSV Invite switch and normal Invite-Link approval can independently make it pending. Group-change and delete approvals use durable action-request records that are revalidated when a reviewer acts.
Profiles and Packs Can Add Other Approval Behavior
User Type Profiles and Invite Packs also carry approval-related configuration for the account-creation stage. Do not assume turning off a global workflow switch guarantees every account becomes immediately usable; review the selected Profile/Pack rules as well.
Plan and Feature Boundaries
The Approval Workflow feature starts at Pro. Frontend group changes and deletion themselves are Max/All Access user-manager capabilities, so their approval toggles matter only when the underlying action is available and enabled.
Recommended Rollout
- Enable approval only for the workflows that truly require review.
- Grant
qcfum.admin.approvalsonly to trusted reviewers. - Test each enabled workflow with the real delegated staff group.
- Verify both approval and rejection outcomes before production use.
- After group/protection/tier changes, retest pending action approvals because execution is revalidated at decision time.
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.