Publish, Unpublish, and Test User Type Profiles

The Published flag controls whether a User Type Profile is available to current onboarding workflows. An unpublished Profile is not merely hidden from a dropdown: current server-side Profile lookup also refuses it.

That means Profile publication can affect Direct Create, Invite Packs, existing Invite Links, and Max/All Access Join Codes that depend on that Profile.

Publish or Unpublish a Profile

Open QCFUM Administrator → Profiles, edit the Profile, and set or clear Published. Saving the Profile keeps the row and its configuration; unpublishing does not delete it or erase historical references.

Published Profiles are loaded for current workflows subject to the current tier allowance. QCFUM also applies its Profile-count limit when deciding which published records are available.

What Becomes Unavailable

  • Direct Create: the selected Profile must resolve as a current published Profile or QCFUM returns “Select a valid User Type Profile.”
  • New Invite Links: the selected Invite Pack must point to a current published Profile. If not, QCFUM refuses the invitation.
  • Existing Invite Links: account completion rechecks the stored Profile ID. If that Profile is unpublished or unavailable at the current tier, the recipient cannot complete the account until the dependency is restored.
  • Join Codes: current usable-code queries require the Join Code, Invite Pack, and Profile all to be published. Completion rechecks the Pack/Profile again.

Test a Profile Before Production Use

  1. Map the Profile only to safe Joomla destination groups.
  2. Publish it and test Direct Create as the actual non-Super-User staff group.
  3. If an Invite Pack depends on it, create a test Invite Link and confirm the recipient path.
  4. If Max/All Access Join Codes depend on it, verify the Join Code appears as usable and completes correctly.
  5. Unpublish the Profile temporarily and confirm each dependent workflow fails closed rather than silently using a different Profile.
  6. Republish it and confirm service returns without rebuilding historical data.

Tier Availability Still Applies

Publication does not override the tier. Basic, Pro, and Max/All Access load only the number of Profiles permitted by the current Effective tier. Extra Profiles are preserved after a downgrade, but an over-tier Profile can be locked or unavailable even if its Published value remains 1.

Operational Rule

Use unpublish when you want to stop a Profile from being used while preserving its configuration. Before doing so, inventory the Invite Packs and Join Codes that depend on it. Publication is a live dependency, not just an administrative display preference.

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.