Scope Custom Email Templates to All Plans or Selected Plans

Use Plan scope only for triggers with reliable Plan context and understand that every published matching Core/Custom template sends independently rather than one overriding another.

This guide follows the accepted QC Memberships & Meetings 2.0.21 implementation and applies to Max / All Access; administrator. This category covers QCMM email behavior and unattended automation: Core and Custom templates, tiered HTML capability, event recipients/tokens, reminders, lifecycle tasks, entitlement validation, and background resource synchronization. When older walkthrough or project-manual wording conflicts with 2.0.21 source or later accepted Authorized-Domain behavior, the current implementation takes precedence.

Before You Begin

• Confirm Joomla Mail can send successfully before diagnosing a QCMM template or notification problem.
• Identify whether the message is a Core template or administrator-created Custom template and which tier enables the desired HTML/custom behavior.
• Check the relevant Scheduled Task when the event is intentionally asynchronous, especially reminders, lifecycle transitions, entitlement, or resource mirroring.

Current QCMM Behavior

Step-by-Step Workflow

1. Open Email and identify the Core or Custom template/event involved.
2. Review publication, format, recipient, Plan scope, token use, and current tier capability.
3. Use Send Test when appropriate to verify rendering and Joomla Mail transport separately from the real event.
4. Trigger the smallest safe real event or relevant Scheduled Task.
5. Confirm the intended recipient receives one correct message and that retry/duplicate-prevention state is healthy.

Scope Custom Email Templates to All Plans or Selected Plans

Use Plan scope only for triggers with reliable Plan context and understand that every published matching Core/Custom template sends independently rather than one overriding another is part of the current QCMM 2.0.21 behavior. Treat the stored QCMM record and server-side authorization as authoritative: frontend controls guide the user, but QCMM still validates identity, ownership/access, current object state, entitlement, and request integrity when an action is submitted.

Keep the distinction between a reusable Plan definition and a purchased subscription snapshot. Administrators can improve or retire future catalog offers without rewriting the commercial and access context that belongs to an existing membership unless a dedicated migration/change workflow intentionally does so.

Current Details That Matter

• Basic supports plain-text email, Pro+ supports HTML, and administrator-created trigger/recipient/Plan-scoped Custom templates require Max/All Access.
• Core and Custom templates are additive; not every internal Core metadata event is selectable when creating a new Custom template.

How This Fits into QC Memberships & Meetings

This category covers QCMM email behavior and unattended automation: Core and Custom templates, tiered HTML capability, event recipients/tokens, reminders, lifecycle tasks, entitlement validation, and background resource synchronization. A reliable QCMM configuration keeps Joomla authoritative for users, groups, access levels, sessions, mail transport, and Scheduled Tasks while QCMM owns Plan, subscription, billing, scheduling, Meeting, Custom Field, resource, and member-facing state.

For Scope Custom Email Templates to All Plans or Selected Plans, verify the behavior with the role that will actually use it. Administrator, member, Host, and Fulfillment Editor experiences intentionally differ. A successful test as Super User does not prove that a normal user has the correct ownership, access, timing, or feature entitlement.

Permissions, Entitlement, and Data Safety

• Joomla menu access, QCMM object ownership/access, role-specific permissions, and commercial feature entitlement are separate checks.
• QCMM re-authorizes state-changing requests server-side; never treat a visible or hidden frontend control as the security boundary.
• Do not expose PayPal credentials, encrypted settings, legacy keys, private room credentials, or other secrets in screenshots, URLs, public documentation, or community posts.
• Preserve subscription, billing, booking, attendance, Custom Field, credit, and entitlement history when correcting a problem; current QCMM is designed to repair in place rather than erase evidence.
• When Effective tier falls, premium configuration/history is preservation-first: features can become unavailable without deleting the saved data.

Verify the Result

• The intended recipient receives one correctly rendered message with resolved current-context tokens.
• Plain text versus HTML behavior matches the current Effective tier.
• Reminder/lifecycle messages occur at the expected task cadence and are not duplicated by manual retry.
• Entitlement and Resource Reservation background tasks remain separate from normal frontend page rendering and customer requests.

Common Mistakes to Avoid

• Diagnosing a Joomla Mail transport failure as a QCMM template-token problem.
• Assuming every internal Core metadata event is selectable for a new Custom template.
• Putting remote entitlement or resource-service calls back onto normal frontend rendering paths.
• Changing task cadence to mask a configuration/data problem instead of diagnosing the failing layer.

Troubleshooting

• Test Joomla Mail independently, then template publication/format/recipient/tokens, then the event/task that triggers delivery.
• Check duplicate-prevention and prior send state before manually rerunning a reminder or lifecycle event.
• Reproduce the exact action with the smallest safe test and record the user role, Plan/subscription/booking/billing identifiers, current state, and time zone where relevant.
• If a control is missing, check Joomla access, QCMM permission/ownership, record state, Effective tier, and task health before assuming packaged files are damaged.
• If behavior is asynchronous, inspect the owning Scheduled Task and its last result instead of repeatedly performing the business action.
• After a correction, rerun the same scenario from the real frontend; a successful Administrator save alone is not end-to-end verification.

Operational Best Practice

Keep Joomla Mail healthy and keep the five task cadences canonical. Use Core templates for standard events, add Custom templates only where Max-level trigger/recipient/Plan scoping is actually needed, and test both rendering and the real event path without creating duplicate messages.

Community Discussion

Want to compare membership or Meeting workflows, share practical QCMM tips, or discuss how other Joomla site owners use this feature? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.