Configure QCFUM Administrator Permissions
QCFUM 2.0.4 separates Administrator responsibilities so a Joomla administrator can delegate specific component duties without granting every QCFUM management capability. Configure these permissions in Joomla’s Permissions interface for QC Frontend User Manager.
The component’s Manage Settings, Licensing, and Updates action covers QCFUM’s own settings/entitlement/update controls; installing an available Joomla extension update still requires the Joomla Installer permission as well.
Current Administrator Actions
| Permission | What it controls |
|---|---|
| Manage Settings, Licensing, and Updates | Save component settings; refresh/clear legacy entitlement state; start eligible Max Preview; check updates; repair entitlement task structure. |
| Manage Scheduled Automation | Change QCFUM Scheduled Automation settings. |
| Manage Approvals | Configure approval rules and approve/reject pending onboarding or User Manager actions. |
| Manage User Type Profiles | Add, edit, and delete Profiles. |
| Manage Invite Packs | Add, edit, and delete Invite Packs. |
| Manage Join Codes | Add, edit, and delete Join Codes when the tier permits them. |
| Manage Email Templates | Edit templates, send tests, publish/duplicate/delete templates, and retry queued mail where available. |
| Manage Insights | Use administrative Insights controls such as resetting the reporting baseline. |
| Manage Frontend Design and Text | Change frontend appearance/text and Max custom CSS where entitled. |
Component Access Is Separate
core.manage controls baseline access to the component. core.admin remains the Joomla administrative override. The fine-grained QCFUM actions then determine which management areas and POST tasks a non-Super administrator may use.
Compatibility Fallback on Upgraded Sites
If one of the newer QCFUM Administrator actions has not been explicitly configured in the component asset, 2.0.4 falls back to the user’s component core.manage authority. Once a QCFUM action is configured, its own Joomla ACL result is used. This is why administrators upgrading an older site should review the component Permissions screen instead of assuming the new actions are already restrictive.
Use Least Privilege
- A support operator may need Status/Settings access but not Profiles, Join Codes, or design changes.
- A workflow reviewer may need Approvals without permission to change licensing or templates.
- A content/communications administrator may need Email Templates and Frontend Design without user-management authority.
- Do not give
core.adminmerely to avoid configuring the QCFUM actions.
Configure and Verify
- Open Joomla’s component Permissions for QC Frontend User Manager.
- Select the exact Joomla group used by the delegated administrator role.
- Set only the required QCFUM Administrator actions to Allowed; explicitly deny capabilities the role should not have when appropriate for your ACL design.
- Sign in with a non-Super-User test account from that group.
- Verify both navigation visibility and a real save/action in each granted area, then verify an intentionally withheld action is refused.
Joomla Installer Permission for Updates
QCFUM can show and check its update state under the Settings/Status permission, but the actual Joomla extension update handoff is shown only when the user also has core.manage for com_installer. Keep that distinction when designing a role that may inspect updates but not install extensions.
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.