How Profile Limits Behave After a QCFUM Downgrade
QCFUM uses a preservation-first downgrade model. Dropping from Max to Pro or Basic does not delete User Type Profiles that exceed the new tier. Instead, current use and administration are limited by the lower Effective tier.
This matters because the saved Profile rows remain part of the installation even when only a subset can be used or edited.
Current Profile Allowances
| Effective tier | Profile allowance | Add/Delete |
|---|---|---|
| Basic | 1 Profile | Cannot add or delete; can edit the included allowed Profile |
| Pro | 10 Profiles | Can add and delete within the tier allowance |
| Max / All Access | Unlimited | Can add and delete without a product count limit |
How QCFUM Chooses Allowed Records
For administrative edit/delete checks, QCFUM determines the allowed set by Profile ID in ascending order and applies the current numeric limit. Extra rows are preserved but return a locked/outside-tier message when an administrator tries to edit or delete them.
Published frontend Profile loading is also capped by the current tier. Because publication is filtered as part of runtime loading, keep the first allowed records deliberately configured and published rather than relying on record order accidentally.
What a Downgrade Does Not Do
- It does not delete extra Profile rows.
- It does not erase Profile group mappings, approval flags, welcome-email flags, descriptions, or publication values.
- It does not delete historical created-user or invite records.
- It does not rewrite dependent Invite Packs to a different Profile automatically.
Why Dependent Workflows Can Stop
An Invite Pack or Invite Link that references a Profile unavailable under the current tier can fail current runtime validation. QCFUM intentionally rechecks the Profile when an Invite Link is created or completed. Max-only Join Code workflows also recheck the current Pack/Profile dependency.
After a downgrade, test the Profiles and Packs that remain intended for active use instead of assuming preserved configuration is automatically executable.
What Happens After Upgrade
When the Effective tier again includes the preserved records, the stored Profile rows are available under the restored allowance without recreating them. This is why QCFUM keeps over-tier records rather than deleting configuration on downgrade.
Community Discussion
Want to compare QCFUM onboarding designs, User Type Profiles, Invite Packs, or safe Joomla group mappings? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.