Publish, Unpublish, Delete, and Troubleshoot Invite Packs

Invite Pack lifecycle changes affect live onboarding. Because QCFUM rechecks the Pack and Profile during current workflows, unpublishing or deleting a Pack can stop both new and existing self-service paths that depend on it.

Historical invite/reporting rows are preserved when a Pack is deleted, but preserved history does not make the deleted Pack executable.

Publish and Unpublish

A published Pack can be loaded for current Invite Link workflows subject to the current tier allowance. Unpublishing keeps the Pack row but removes it from published Pack lookup.

That blocks creation of new Invite Links from the Pack. Existing Invite Link completion also requires the Pack to resolve as currently published/available, so an existing recipient can be stopped until the Pack is republished. Usable Join Codes likewise require a published Pack and published Profile.

Delete an Invite Pack

Pack deletion starts at Pro and QCFUM refuses deletion of a Pack preserved outside the current tier allowance. The delete operation removes the Pack configuration row and records an audit event; it explicitly leaves historical invite/reporting records intact.

Deletion does not cascade into existing invitation or Join Code rows. Those dependencies can become unusable because their Pack no longer exists. Review them before deleting.

Troubleshoot an Unusable Pack

  1. Confirm the Pack is Published.
  2. Confirm it is within the current Effective tier’s Pack allowance.
  3. Confirm its User Type Profile still exists, is published, and is within the current Profile allowance.
  4. Confirm the Profile maps only to valid non-protected Joomla groups.
  5. Confirm the selected Email Template still exists and is published if QCFUM should send email.
  6. Check whether the invitation itself is pending approval under the granular Invite-Link approval setting.
  7. For existing Invite Links, check status and stored expiration.
  8. For Join Codes, also verify Max/All Access, Join Code publication, expiration, usage limit, and the current Pack/Profile relationship.

Downgrade Behavior

Basic includes one Invite Pack, Pro includes up to 10, and Max/All Access are unlimited. QCFUM preserves Packs that exceed a lower tier after downgrade but can lock or exclude them from current use. Upgrading restores access under the higher allowance without recreating the rows.

Prefer Reversible Changes First

When retiring a Pack, unpublish it first and test the impact. Update or retire dependent Join Codes, let active Invite Links complete where appropriate, and only then delete the Pack if you no longer need the configuration. This preserves a clear recovery path while you validate production behavior.

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.