Configure Frontend Fulfillment Editor Groups

Choose Plan-specific Joomla groups allowed to use the Field Fulfillment workspace; Host status and Joomla administrator access alone do not substitute for the configured group authorization.

This guide follows the accepted QC Memberships & Meetings 2.0.21 implementation and applies to Max / All Access; administrator. This category covers Max Custom Fields and fulfillment plus Plan Resources: subscription-specific field snapshots, customer/admin editability, Plan-specific Fulfillment Editor authorization, and protected member resources. 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

• Design Custom Fields around information that belongs to a specific purchased subscription rather than the Joomla user globally.
• Decide which values the customer enters at checkout, can view later, can edit in Member Area, or require administrator/Fulfillment Editor completion.
• For protected Downloads, verify the resource belongs to the intended Plan/group and use QCMM delivery rather than exposing the storage path directly.

Current QCMM Behavior

Step-by-Step Workflow

1. Open the Custom Field definition or Plan Custom Fields assignment and confirm the field belongs to the intended workflow.
2. Set type, required state, customer entry/view/edit behavior, and Plan ordering deliberately.
3. Create or use a test subscription so the value becomes part of that subscription snapshot.
4. If fulfillment is required, test with a member of the configured Plan-specific Fulfillment Editor Joomla group.
5. Verify Member Area Additional Information and administrator/subscription display show the correct saved value and fulfillment state.

Frontend Fulfillment Editor Groups

Choose Plan-specific Joomla groups allowed to use the Field Fulfillment workspace; Host status and Joomla administrator access alone do not substitute for the configured group authorization 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

• Joomla groups per Plan are limited to Basic 1, Pro 2, and Max/All Access unlimited; group access should be verified with a normal member account.
• Frontend Field Fulfillment authority comes from the Plan-specific Fulfillment Editor Joomla group; Host status or generic administrator status is not a substitute.
• Scheduling is Max/All Access and includes customer conflict protection, booked-capacity safety, rescheduling, No Show handling, optional courtesy replacement, reminders, and calendar integration.
• Existing purchased appointments and their history are preserved if the installation later drops below Max.

How This Fits into QC Memberships & Meetings

This category covers Max Custom Fields and fulfillment plus Plan Resources: subscription-specific field snapshots, customer/admin editability, Plan-specific Fulfillment Editor authorization, and protected member resources. 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 Configure Frontend Fulfillment Editor Groups, 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

• Each subscription retains its own Custom Field values even when the same Joomla user owns multiple memberships.
• Customer-visible/editable behavior matches the purchased subscription snapshot and current allowed workflow.
• Only the configured Plan-specific Fulfillment Editor group can perform fulfillment actions.
• Protected Downloads require an eligible authenticated subscription and are delivered as authorized attachments rather than arbitrary remote fetches.

Common Mistakes to Avoid

• Storing subscription-specific fulfillment data as if it were a single global Joomla user profile value.
• Assuming Host or Joomla Administrator status automatically substitutes for the Plan-specific Fulfillment Editor group.
• Displaying internal/admin-only field values to customers because the field exists on the Plan.
• Turning Plan Resources into an unrestricted proxy for arbitrary remote URLs.

Troubleshooting

• Check Plan/Host assignment, availability, notice window, capacity/holds, customer conflicts, and current booking state in that order.
• Confirm the site/user time-zone context before treating a displayed time difference as a stored-data error.
• Check the field definition, Plan assignment, subscription snapshot, customer view/edit flags, and Fulfillment Editor group separately.
• If a value changed concurrently, reload the current subscription state before overwriting newer fulfillment/customer edits.
• 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.

Operational Best Practice

Keep fields purposeful and minimize sensitive data. Use stable field tokens, limit customer/admin editability to the real workflow, delegate fulfillment only to the configured Plan-specific groups, and keep protected Downloads behind QCMM authorization instead of publishing direct file URLs.

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.