Configure and Use Approval Reminder Automation
Set reminder enablement, first delay, repeat interval, and maximum reminders; explain dependency on Scheduled Automation and administrator recipients.
This guide follows the accepted QC Frontend User Manager 2.0.4 implementation and applies to Pro+; administrator. QCFUM delegates selected Joomla user-onboarding and management workflows without making frontend staff Joomla backend administrators. When older manuals or walkthrough wording differs from the current source or accepted keyless-entitlement behavior, the current implementation takes precedence.
Before You Begin
- Confirm Effective Pro/Max access before relying on CSV, approval, or temporary-access features.
- Preview imports before committing them and use a small controlled test first.
- Keep Scheduled Automation healthy whenever temporary access already exists, even if commercial automation is turned off.
Step-by-Step Workflow
- Open Approval Queue as an account with the required approval permission.
- Filter/locate the pending onboarding or protected user-management action.
- Inspect the target user/invite, requested operation, submitter, and current group/protection context.
- Approve only if the action remains authorized under the current entitlement, ACL, and safeguards; otherwise reject it.
- Confirm the durable request moves to its resulting state and that the underlying Joomla user/invite action matches the decision.
Scheduled Automation Responsibilities
| Responsibility | Behavior |
|---|---|
| Temporary-access expiration | Security enforcement runs first and can remain active even when commercial Pro automation is off. |
| Invite nudges | Automatic reminder delivery for eligible pending Invite Links. |
| Stale-invite auto-cancel | Optional cleanup of invitations that exceed configured aging rules. |
| Email retry | Retries eligible failed queued mail where Pro+ functionality applies. |
| CSV cleanup | Maintenance of retained import-support data according to configured policy. |
| Approval reminders | Reminder processing for durable pending approval requests. |
| Administrator summary | Optional operational summary where configured. |
| Audit cleanup | Retention maintenance for QCFUM-owned audit/history support data. |
Temporary-access expiration is treated as a security obligation. It is processed before QCFUM decides whether optional Pro commercial automation is both entitled and enabled.
Set reminder enablement, first delay, repeat interval, and maximum
Set reminder enablement, first delay, repeat interval, and maximum reminders. In QCFUM 2.0.4, this must be evaluated together with the current Effective tier, the Joomla/QCFUM permissions of the acting account, and target/workflow safeguards. QCFUM is designed to fail closed around protected users and sensitive actions rather than trusting the presence of a frontend button as authorization.
For Configure and Use Approval Reminder Automation, test the exact workflow with a safe non-administrator account and a deliberately chosen target. QCFUM’s frontend presentation is not the authorization boundary: a control can be visible while the server still refuses an unsafe target, an unavailable tier, an invalid workflow state, or a group change that violates administrator-defined safeguards.
Dependency on Scheduled Automation and administrator recipients
explain dependency on Scheduled Automation and administrator recipients. In QCFUM 2.0.4, this must be evaluated together with the current Effective tier, the Joomla/QCFUM permissions of the acting account, and target/workflow safeguards. QCFUM is designed to fail closed around protected users and sensitive actions rather than trusting the presence of a frontend button as authorization.
For Configure and Use Approval Reminder Automation, test the exact workflow with a safe non-administrator account and a deliberately chosen target. QCFUM’s frontend presentation is not the authorization boundary: a control can be visible while the server still refuses an unsafe target, an unavailable tier, an invalid workflow state, or a group change that violates administrator-defined safeguards.
How This Fits into QCFUM
CSV, durable approvals, and temporary-access expiration add scale and control. Security enforcement is deliberately separated from optional commercial automation.
A reliable QCFUM configuration keeps Joomla authoritative for real user accounts while QCFUM owns the delegated workflow, attribution, approval, automation, and safety rules around those accounts. This separation matters during upgrades and downgrades: preserving QCFUM records does not mean every preserved premium feature remains usable at a lower Effective tier.
Security and Data-Protection Notes
- Use least privilege for menu access and QCFUM ACL; grant staff only the actions required for their role.
- Never share passwords, invite tokens, API credentials, or private account data in screenshots, support requests, or custom email content.
- Treat Super Users and equivalent administrative-capability accounts as protected even when a UI configuration appears permissive.
- Verify destructive or access-changing actions with a safe test account before enabling them for production staff.
- Remember that uninstall/reinstall is not a supported method for wiping QCFUM business data or resetting entitlement/preview history.
Verify the Result
- The relevant Joomla Scheduled Task is published/healthy and security expiration behavior is not accidentally disabled with commercial automation.
- Reload the real frontend/Administrator view rather than relying only on a saved form message.
- Repeat the critical test using the exact non-Super-User group that will operate the workflow.
Common Mistakes to Avoid
- Assuming an old pending approval guarantees the action can still run after groups, protections, or entitlement change.
- Disabling the Scheduled Automation task while existing temporary-access users still depend on expiration enforcement.
- Testing only as Super User instead of the actual delegated staff group.
- Changing multiple security/workflow settings at once during troubleshooting, making the real cause difficult to identify.
Troubleshooting
- If a control or tab is missing, check Effective tier, QCFUM ACL, menu access, and feature configuration before assuming installation damage.
- If a user cannot be selected or changed, check protected groups/IDs, core administrative protection, visibility/editability rules, destination-group rules, and the delegated manager’s exact permissions.
- If onboarding stalls, inspect the stored workflow status (invite, approval, import, temporary access) rather than deleting the record and starting over immediately.
- If automation does not run, verify Joomla Scheduled Tasks and distinguish the hourly Entitlement Revalidation task from the separately configured Scheduled Automation task.
- If email does not arrive, verify Joomla mail transport independently, then inspect QCFUM template publication, recipient/address, queue state, and retry eligibility.
Operational Best Practice
Keep onboarding definitions simple enough that staff can select the correct Profile/Pack without guessing. Test every delegated workflow with the real staff Joomla group, keep entitlement/tasks healthy, and preserve an Administrator recovery path. When changing user-management safeguards, verify both a target that should be allowed and a protected target that must still be refused.
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.