QC Frontend User Manager Administrator Tabs Explained
QCFUM 2.0.4 organizes Administrator management into eleven current tabs: About, Support, Status, Settings, Email, Profiles, Invite Packs, Join Codes, Tracker, Insights, and CSS. The tab bar is permission-aware, so two administrators can legitimately see different sets of tabs.
A hidden tab normally means the logged-in Joomla account lacks the corresponding QCFUM administrative action; it does not mean the underlying data was deleted.
Current Administrator Tabs
| Tab | Purpose |
|---|---|
| About | Product orientation: controlled frontend onboarding, workflow/automation, protected user management, and current entitlement banner. |
| Support | Support Center, account/product resources, walkthrough, and safe environment/support information. |
| Status | Entitlement, Base/Effective tier, task integrity, Scheduled Automation, installation identity, tier feature snapshot, and extension updates. |
| Settings | Authorized-Domain entitlement controls, general workflow settings, safeguards, automation/approval behavior, frontend text/design controls available to the acting administrator. |
| Core/custom notification templates, plain/HTML capability, testing, publication, and delivery-related management. | |
| Profiles | User Type Profiles that constrain approved onboarding destinations and behavior. |
| Invite Packs | Reusable invitation configurations tied to Profiles and email/invite behavior. |
| Join Codes | Max/All Access reusable self-service code records tied to Invite Packs. |
| Tracker | Administrator-facing onboarding/invitation tracking and approval-related operational records. |
| Insights | QCFUM activity and creator-oriented reporting/scorecard information. |
| CSS | Max/All Access custom frontend CSS editor and saved presentation overrides. |
Why Tabs Can Be Missing
QCFUM builds the visible tab list from Joomla/QCFUM ACL actions. About and Support are available once the administrator can enter QCFUM. Other areas require their respective management permissions—for example Settings/Status, Email Templates, Profiles, Invite Packs, Join Codes, Insights, or Design.
The Settings tab has a special case: it can be visible to an administrator who has Settings permission or Design permission because frontend presentation settings live there alongside general settings.
Plan Entitlement and ACL Are Different
Seeing a tab does not automatically unlock every control inside it. A user can have Joomla permission to manage an area while the current Effective tier still locks a Pro- or Max-only capability. Conversely, buying Max does not grant an administrator an ACL action they do not already have.
Use the Tabs as a Diagnostic Map
- Start with Status for entitlement, task, installation, and update health.
- Use Settings for site-wide workflow and entitlement configuration.
- Use Profiles and Invite Packs before troubleshooting frontend onboarding choices.
- Use Tracker when the question is what happened to an onboarding or invitation record.
- If an expected tab is absent, inspect Joomla component permissions for the exact administrator group before assuming a plan or installation problem.
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.