Joomla Menu Access, QCFUM ACL, and Plan Entitlement: Three Separate Gates
Access to a QCFUM frontend workflow is determined by three different layers: Joomla menu/access-level visibility, QCFUM action permissions, and the current QCFUM feature entitlement. These layers solve different problems and should be configured separately.
A page being visible does not prove that every action on that page is authorized. QCFUM 2.0.4 rechecks protected actions on the server.
Gate 1 — Joomla Menu Access
The Joomla menu item controls who can reach the frontend QCFUM page through normal site navigation. Use an appropriate Joomla Access Level for the staff audience. Menu visibility is presentation/access routing; it does not by itself grant Create, Invite, CSV, tracking, or existing-user-management authority.
Gate 2 — QCFUM Action Permissions
| Frontend action | Purpose |
|---|---|
| Create Users from the Frontend | Direct Create and compatible create workflows. |
| Send Invite Links from the Frontend | Create/send invitations. |
| Import Users by CSV from the Frontend | Preview/process eligible CSV onboarding. |
| Manage Own Invite Links | View, resend, cancel, and track permitted invitation activity. |
| Use the Frontend User Manager | Perform enabled Max-level management of eligible existing users. |
QCFUM also has separate Administrator actions for settings, automation, approvals, Profiles, Invite Packs, Join Codes, email templates, Insights, and frontend design/text. Super Users pass these checks; other accounts are evaluated through the component ACL.
Compatibility Behavior Matters
For upgraded sites, QCFUM preserves the older access-level model until a newer QCFUM action has actually been configured in Joomla Permissions. Administrator actions without an explicit rule fall back to component core.manage; frontend actions without an explicit rule preserve authenticated/menu-access compatibility. For delegated staff, explicitly configure the QCFUM actions instead of assuming an unconfigured action means Denied.
Gate 3 — Current Plan Entitlement
The plan controls whether the feature itself is available. For example, CSV onboarding requires Pro or higher and the Frontend User Manager requires Max or All Access. An ACL grant cannot unlock a feature the current Effective tier does not include, and a paid tier does not override a missing Joomla/QCFUM permission.
Example
A staff member can see the Dashboard because the menu allows their group, and can have Create Users permission, while CSV remains unavailable because the site is Basic. After an upgrade to Pro, CSV still should not become a delegated staff capability until Import Users by CSV is also granted to that staff group.
Test All Three Gates
- Sign in as a non-Super-User account in the real staff group.
- Confirm the intended QCFUM menu item is visible and an unrelated group cannot reach it.
- Confirm only the dashboard tabs/actions granted to the staff role appear.
- Confirm tier-locked features remain unavailable even when the user has broad Joomla access.
- Test at least one denied action and one protected target so server-side safeguards are verified, not just the UI.
Community Discussion
Want to compare Joomla user-management safeguards, share practical QCFUM configuration ideas, or discuss how other administrators delegate frontend workflows? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.