Use Temporary Access During Direct User Creation
Pro, Max, and All Access can attach an optional Access Expires date when a frontend manager creates a user directly. QCFUM stores the expiration with the created-user tracking record and later enforces it as a security obligation.
Temporary access is intended for ordinary delegated accounts. QCFUM deliberately refuses to automatically block protected Joomla administrative accounts when an expiration is reached.
Set an Expiration
- Open Create User and enter the normal account details.
- Choose an approved User Type Profile.
- If the current Effective tier is Pro or higher, optionally select Access Expires.
- Submit the user. QCFUM stores the selected date as an expiration at 23:59:59 for its UTC-oriented scheduled comparison and records it with the created-user row.
- Verify the expiration in the QCFUM tracking details after creation.
How Expiration Is Enforced
When an active tracked user reaches access_expires_at, QCFUM Scheduled Automation checks the Joomla account. For an ordinary user, it sets Joomla block=1 and changes the QCFUM tracking status to expired.
If the Joomla user no longer exists, QCFUM records expired_missing. If the target has protected administrative capability such as core.admin, core.login.admin, or core.manage, QCFUM does not block the account and records expired_protected for administrator attention.
The Scheduled Task Is Part of the Security Model
Creating a temporary-access record causes QCFUM to keep the Scheduled Automation task available. Even if optional commercial automation is disabled later, QCFUM can keep the Joomla task published while active temporary-access users still depend on expiration enforcement.
Do not disable or remove the Scheduled Automation task while temporary access remains active.
Verify Before Production Use
- Test with an ordinary non-administrator account and a near-term expiration.
- Confirm the Scheduled Automation task is published and actually running.
- Confirm the user becomes blocked after expiration and the QCFUM tracking status changes.
- Never use temporary-access automation as the control mechanism for Super Users or equivalent protected administrator accounts.
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.