How Profile Limits Behave After a QCFUM Downgrade
Explain deterministic earliest-record allowance, preservation of extra rows, locked/inactive presentation, and automatic reuse when the required tier returns.
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
- Decide which Joomla groups are genuinely safe onboarding destinations.
- Separate friendly onboarding choices from raw group IDs by using Profiles.
- Test a Profile/Pack with a non-administrator account before broad staff use.
Step-by-Step Workflow
- Open QCFUM Administrator and choose Profiles or Invite Packs as appropriate.
- Create/select the configuration record and give it a clear staff-facing title.
- Choose only approved Joomla destination groups and workflow options.
- Save and publish the record when it is ready for use.
- Test it from the unified frontend with a delegated non-Super-User account.
- After any tier downgrade, verify over-limit records are preserved/locked rather than deleting them to make the UI look cleaner.
Current QCFUM Plan Matrix
| Tier | Created users / creator | Destination groups | Profiles | Invite Packs | Key capabilities |
|---|---|---|---|---|---|
| Basic | 10 created users per frontend creator | 1 destination group | 1 active Profile | 1 active Invite Pack | Direct creation, Invite Links, manual Nudge, Recent Users/Tracker, frontend text/design, safeguards, plain/custom email templates. |
| Pro | 100 created users per frontend creator | 5 destination groups | 10 Profiles | 10 Invite Packs | Adds CSV Import, approval workflows, Scheduled Automation, automatic nudges, temporary access, email retry, and HTML email. |
| Max / All Access | Unlimited | Unlimited | Unlimited | Unlimited | Adds Join Codes, full Frontend User Manager, Bulk Actions, and Custom CSS. |
These are QCFUM product allowances, not Joomla ACL. A user can have a high QCFUM tier and still be denied an action by Joomla/QCFUM permissions or target-specific protection. Downgrades preserve records rather than deleting configuration that temporarily exceeds the lower tier.
Deterministic earliest-record allowance, preservation of extra rows, locked/inactive presentation,
Explain deterministic earliest-record allowance, preservation of extra rows, locked/inactive presentation, and automatic reuse when the required tier returns. 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 How Profile Limits Behave After a QCFUM Downgrade, 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 How Profile Limits Behave After a QCFUM Downgrade, 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 How Profile Limits Behave After a QCFUM Downgrade, 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
Profiles and Invite Packs make onboarding repeatable. They are configuration records rather than ownership relationships; users created through them remain normal Joomla users.
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
- 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
- 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.