Delete a User Type Profile Without Losing Historical Context

Deleting a User Type Profile removes the reusable Profile configuration row; it does not erase the historical QCFUM records that previously referenced that Profile. QCFUM explicitly reports that historical reporting records are not deleted.

Deletion still needs care because QCFUM 2.0.4 does not automatically block a Profile delete just because an Invite Pack points to it.

Deletion Requirements

Profile deletion starts at Pro. Basic can use and edit the included Profile but cannot delete Profiles. QCFUM also refuses deletion when the Profile is preserved outside the current tier allowance; upgrade first if you need to remove that locked record.

Check Dependencies Before Deleting

Before selecting Delete, review Invite Packs for any Pack whose Profile is the one you plan to remove. A Pack stores the numeric profile_id. QCFUM does not cascade the Profile deletion into Pack cleanup.

Also review Max/All Access Join Codes that use those Packs. A Join Code depends on its Invite Pack and that Pack’s current Profile. Removing the Profile can make the Pack unusable and therefore make dependent Join Codes fail validation.

What QCFUM Deletes—and What It Keeps

The delete operation removes the selected row from #__qcfum_group_profiles and writes an audit event containing the Profile ID and title. It does not delete created-user history, invite history, reporting/audit records, or Joomla users that were previously created through the Profile.

Historical records may retain the former Profile ID even though the live configuration row no longer exists. That is intentional historical context, not proof that the Profile is still usable.

Safe Deletion Procedure

  1. Identify every Invite Pack that references the Profile.
  2. Move each Pack to a replacement published Profile or retire the Pack first.
  3. Verify any dependent Join Codes after the Pack change.
  4. Confirm no current operational workflow still needs the Profile.
  5. Delete the Profile from the Administrator Profiles tab.
  6. Test Direct Create, Invite Links, and Join Codes that were affected by the change.

When Unpublish Is Better

If you may need the Profile again, unpublish it instead of deleting it. Unpublish preserves the configuration and immediately removes it from current published Profile lookups. That gives you a reversible retirement path while you validate dependencies.

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.