Review QCFUM Onboarding Context for an Existing User

When an existing Joomla account was created through QCFUM and still has a matching QCFUM created-user record, the expanded Users row adds a QCFUM Onboarding section. That context explains how the account entered the system; it does not make QCFUM the owner of the Joomla user.

Accounts created outside QCFUM can still be managed when they meet the Frontend User Manager scope rules, but they will not automatically have this onboarding section.

What the Onboarding Section Shows

QCFUM can show the onboarding Source, User Type Profile, Submitted By, onboarding Status, Access Starts, Access Expires, and the QCFUM-created timestamp.

Where the Context Comes From

The Users workspace reads QCFUM’s created-user history and joins the stored Profile ID to the current Profile title plus the stored creator/submitting Joomla user. Source label is preferred when present, with source type as the fallback.

Submitted By Is Attribution

Submitted By is workflow attribution. It identifies the Joomla user who initiated the QCFUM creation/onboarding record; it does not create a parent-child account relationship and does not give that person ownership of the target Joomla account.

Temporary Access Appears Here

If the onboarding record used QCFUM temporary access, the stored access-start and access-expiration timestamps appear in this section. “No expiration” means the created-user record has no expiration value; it does not disable Joomla’s own account-state rules.

Use Context for Troubleshooting, Not Authorization

Onboarding history can explain why a user is pending, expired, or associated with a particular Profile, but current management actions still use today’s Max entitlement, ACL, source/editable groups, protected-user rules, and individual action settings. Old onboarding history never grants current permission by itself.

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.