Use the QCFUM Status Tab to Check Installation Health
Review version, entitlement, Base/Effective tier, feature snapshot, update state, Entitlement Revalidation health, Scheduled Automation state, installation identity, and available repair/update actions.
This guide follows the accepted QC Frontend User Manager 2.0.4 implementation and applies to All plans; 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
- Take a current Joomla/site backup before installation, upgrade, or structural changes.
- Confirm Administrator access and permission to install extensions and inspect Scheduled Tasks.
- Record the current QCFUM version and Base/Effective tier before entitlement or task changes.
Step-by-Step Workflow
- Open the QCFUM Administrator area that owns the setting/status.
- Record the current version, entitlement, and relevant task state.
- Make the smallest required change and save it.
- Reload the screen and verify the persisted state.
- Run a safe frontend smoke test when the change affects delegated onboarding.
Current Administrator Areas
| Area | Purpose |
|---|---|
| About | Product orientation and version information. |
| Support | Support links and safe environment information. |
| Status | Version, entitlement, updates, installation identity, and task health. |
| Settings | Frontend behavior, safety, automation, text/design, and user-management controls. |
| Core/custom templates, test mail, publication, HTML entitlement, and queue-related configuration. | |
| Profiles | User Type Profiles and approved Joomla group mappings. |
| Invite Packs | Reusable invitation workflow definitions. |
| Join Codes | Max/All Access self-service onboarding codes. |
| Tracker | Administrative onboarding history and approval context. |
| Insights | User-activity reporting controls. |
| CSS | Max/All Access custom frontend CSS workspace. |
Scheduled Automation Responsibilities
| Responsibility | Behavior |
|---|---|
| Temporary-access expiration | Security enforcement runs first and can remain active even when commercial Pro automation is off. |
| Invite nudges | Automatic reminder delivery for eligible pending Invite Links. |
| Stale-invite auto-cancel | Optional cleanup of invitations that exceed configured aging rules. |
| Email retry | Retries eligible failed queued mail where Pro+ functionality applies. |
| CSV cleanup | Maintenance of retained import-support data according to configured policy. |
| Approval reminders | Reminder processing for durable pending approval requests. |
| Administrator summary | Optional operational summary where configured. |
| Audit cleanup | Retention maintenance for QCFUM-owned audit/history support data. |
Temporary-access expiration is treated as a security obligation. It is processed before QCFUM decides whether optional Pro commercial automation is both entitled and enabled.
Version, entitlement, Base/Effective tier, feature snapshot, update state, Entitlement
Review version, entitlement, Base/Effective tier, feature snapshot, update state, Entitlement Revalidation health, Scheduled Automation state, installation identity, and available repair/update actions. 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 Use the QCFUM Status Tab to Check Installation Health, 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.
For Use the QCFUM Status Tab to Check Installation Health, 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.
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.
For Use the QCFUM Status Tab to Check Installation Health, 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.
How This Fits into QCFUM
This category establishes the installation, entitlement, update, and administrative foundation. It should be completed before delegating frontend onboarding to staff.
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
- Status shows the expected Base and Effective tiers for the current Authorized Domain.
- Entitlement Revalidation is healthy at the canonical hourly cadence unless this guide is specifically diagnosing that task.
- The relevant Joomla Scheduled Task is published/healthy and security expiration behavior is not accidentally disabled with commercial automation.
- 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
- Disabling the Scheduled Automation task while existing temporary-access users still depend on expiration enforcement.
- 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.