Reselling Gateway - Article

What Reselling Gateway helps you achieve

Reselling Gateway turns one centrally governed Training Activity into repeatable, privately managed group deliveries. It is intended for providers that want to serve many separate customers, partners, teams, member groups, or local communities without requiring their own administrators to create and operate every cohort manually.

The original Training Activity acts as the provider’s reusable program template. A group lead starts a private delivery through the configured enrollment or checkout route. Eurekos creates a closed clone, moves the initiating participant and associated Transaction record to it, gives that person Contact Manager capability, and allows them to invite the people who should participate.

The process does not have to involve an immediate payment—or any payment at all. Reselling Gateway controls how the private delivery is created and delegated; it does not prescribe how the program is funded.

Depending on the surrounding commercial and administrative model:

• The group lead may pay when starting the delivery.
• Each invited participant may complete their own payment.
• An organization may fund the program centrally.
• Payment may be handled later through invoicing, reimbursement, or another approved process.
• The activity may be free because the provider’s purpose is to facilitate and document the group process.
• A zero-value Transaction may still be created as the platform record for enrollment without representing money received.

Invited participants join through the controlled invitation route. The group then works through the program inside its own private delivery, while the provider retains the standardized learning design, central oversight, reporting, and completion evidence.

This creates a delegated operating model:

Despite its name, Reselling Gateway does not have to represent conventional resale in which a reseller buys places and sells them onward. Its defining purpose is the delegation of a private delivery: a customer-side or group-side coordinator starts and manages a separate instance of the provider’s standardized program.

For example, a professional association may provide a standardized improvement program to thousands of small independent practices or local professional groups. A practice or group lead starts a private delivery, selects or coordinates the required meeting dates, and invites colleagues. The group then works through self-reflection, assessment, collaborative improvement, and documented learning.

Participation may be free, centrally funded, paid individually, or reimbursed after completion. A certificate or other completion evidence can support reimbursement, accreditation, regulatory documentation, or professional recognition without making payment the purpose of the learning workflow.

The association does not have to create and administer every local group itself. It maintains the program template, learning requirements, certification, and reporting framework, while each group manages its own delivery.

The same model can be applied to:

• Professional or membership associations supporting many autonomous local groups
• Partner networks delivering a centrally governed certification program
• Franchise or dealer organizations coordinating local training
• Customer-managed onboarding or implementation programs
• Distributed quality-improvement and compliance initiatives
• Publicly or centrally funded development programs
• Training providers repeatedly offering complex blended programs as private cohorts

The important requirement is that each initiation should create a genuinely separate delivery with its own participants, coordination, dates, Transaction record, and administration. If the person only needs to join an existing delivery or invite others into an already established activity, use another enrollment or invitation model.

Choose Reselling Gateway or another model

Reselling Gateway is not simply a quantity selector or a way to reserve several places. Completing the configured enrollment or checkout creates a new Training Activity.

Use it only when that separate private delivery record is part of the intended operational design.

Understand the original and the clone

The workflow uses two distinct activities:

After successful completion of the configured enrollment or checkout:

• The initiator appears as a participant only in the cloned activity.
• The initiator’s signup Transaction is transferred to the clone.
• The clone receives a Reselling Gateway label and a reference to its parent or original activity.

When investigating participants, funding, dates, attendance, or completion, begin with the clone. The original is the reusable offer, not the final delivery record.

Confirm platform configuration

A platform owner enables Reselling Gateway in the Activities Promote configuration. Once enabled, the option becomes available beneath the activity-level Self enrollment feature. This is a specialist platform feature and is activated only upon request from Eurekos support.

Before publishing a template, confirm:

• The required enrollment or checkout route is configured.
• Commerce, price, tax, currencies, and payment methods are configured where the delivery is paid.
• The intended free or zero-value route has been tested where no payment is required.
• Promotion, Contact Manager, and Invitations capabilities are operational.
• Reselling Gateway is enabled.
• Calendar events created in Calendar are connected to the original activity when initiators must choose delivery dates.
• The private-clone cleanup period is appropriate.
• Permission for the group lead to edit connected Calendar events is deliberately enabled or withheld.
• System emails are branded, localized, and deliverable.
• Finance and support teams understand that the Transaction moves to the clone.
• Teams understand that a Transaction can represent either a paid or zero-value enrollment.

Event modules inside the learning path do not create the date-selection process described in this article. Where the scenario requires the initiator to select meeting dates, an administrator must create Calendar events in Calendar and connect them to the original Training Activity.

Validate the complete configuration through a controlled test before offering it broadly. Include every intended funding route—for example paid initiation, free initiation, individual participant payment, or later external settlement.

Configure the original activity

The original Training Activity serves two purposes: it is the reusable offer presented through the Storefront, and it provides the starting point for every private delivery created through the Reselling Gateway.

Under Activity features, enable Self enrollment, and then select Reselling Gateway within its configuration. This changes the enrollment model: when an initiator successfully completes the configured enrollment or checkout, Eurekos creates a separate private delivery instead of enrolling the person directly in the original activity. The signup and associated Transaction are connected to the new activity, and the initiator becomes its Contact Manager.

Enabling the feature is only one part of the setup. The original activity’s learning structure, descriptions, commercial terms, availability, connected events and communications determine what initiators see and what each new private delivery starts with. Treat the original as a governed template and verify the complete journey before making it available to customers or partners.

To configure the original activity:

1. Create the Training Activity that will serve as the reusable offer.
2. Configure its modules, completion requirements, features, settings and Activity Description. Ensure that the description clearly explains what is being purchased or requested, what the private delivery includes and what the initiator can expect after completing the process.
3. Under Activity features, enable Self enrollment.
4. Within the Self enrollment configuration, select Reselling Gateway.
5. For a paid offering, configure the price, currencies, tax treatment and available payment methods.
6. Where participation can be free, centrally funded or settled outside Eurekos, configure and test the appropriate zero-value or externally funded route. Confirm that the intended user can complete the process without being directed to an unnecessary payment step.
7. When the initiator should be able to choose delivery dates, create the required events in Calendar and connect them to the original Training Activity. The connected events determine which dates can be presented during the Reselling Gateway journey.
8. Configure the relevant enrollment, invitation and participant-facing emails. Include clear information for the initiator in their role as Contact Manager, particularly where they will invite or manage participants after the private delivery has been created.
9. Confirm the intended organization and Storefront visibility, then save and publish the original activity in the appropriate Storefront.
10. Complete a controlled test enrollment or checkout using a participant who is not already a Contact Manager. This ensures that the complete initiation and role-assignment journey is tested.
11. Test every route that will be offered, including paid, free, discounted and externally funded participation where applicable.
12. Validate the resulting private activity and confirm that:
    • A separate private delivery has been created.
    • The initiating signup and Transaction are connected to the new activity.
    • The initiator has become the Contact Manager.
    • The expected learning structure and participant information are available.
    • Selected Calendar events and delivery details are connected correctly.
    • Invitations and emails contain the expected information.
    • An incomplete process does not leave an unintended empty activity behind.

Creating an Event module inside a learning path does not replace the Calendar configuration in step 7. The Event dates section of the Reselling Gateway enrollment process depends on separately created Calendar events connected to the original Training Activity.

Before publishing, review the original activity as a reusable delivery template:

• Activity and Course descriptions
• Module structure and completion requirements
• Certificates, questionnaires and workflows
• Organization and Storefront visibility
• Registration Details and capacity
• Booking preferences and Additional Products
• Prices, currencies, tax and payment methods
• Free or externally funded participation routes
• Connected Calendar events, time zones and video-conference configuration
• Activity-level administrators and instructors
• Participant, invitation and Contact Manager email content

A configuration issue in the original activity can be reproduced in every later private delivery. Changes to the original activity govern future initiations but do not automatically revise private activities that have already been created.

Activity Description before initiation

An initiator opens the original Training Activity in the Storefront to start a private group delivery.

For a learning path using Reselling Gateway, the Activity Description intentionally does not show Modules in this path. The original activity is a reusable program template, and displaying its Calendar Event dates could incorrectly suggest that the private delivery already has a fixed schedule.

Instead, the initiator selects the dates, times, and time zone for the required meetings during enrollment. The resulting private delivery therefore presents the schedule chosen specifically for that group.

The page must still make the program and process understandable.

Explain:

• The learning outcomes and intended group
• The included delivery and expected preparation
• What the initiator can schedule or coordinate
• Whether participation is paid, free, centrally funded, reimbursed, or handled later
• Price and tax where applicable
• What happens after enrollment or checkout
• That the initiator will invite participants into a private copy
• Whether invited participants must complete their own payment
• Who will configure the final webinar link, instructor, location, or other operational details
• Cancellation, funding, reimbursement, and support terms where applicable

Initiator enrollment and connected Calendar events

The initiator selects Enroll on the original Training Activity and continues through the configured enrollment or checkout route.

When Calendar events created in Calendar are connected to the original activity, the enrollment process includes an Event dates section. The connected events provide the reusable meeting content, including their titles, agendas or descriptions, and attachments. Their original dates, times, durations, and intervals are not retained.

The initiator must schedule every connected event. With the standard configuration, each event initially shows:

• Today’s date
• A start time rounded to the next 30-minute interval
• An end time 30 minutes after the proposed start
• The time zone from the initiator’s profile

These values are starting points only. If the original activity contained three meetings one month apart, the checkout does not reproduce that spacing: all three initially use the standard current-date and time values until the initiator changes them.

The date fields maintain a valid range. If Start is moved later than End, End is moved to match Start. If End is moved earlier than Start, Start is moved to match End.

Eurekos Support can configure the time intervals available in the picker—such as 5, 10, 15, or 30 minutes—and a separate standard duration for new Calendar events. When no separate duration is configured, the proposed duration follows the time-picker interval.

If the original Training Activity has no connected Calendar events, the Event dates section is absent. Event modules inside the learning path do not create this section and are not a substitute for connected Calendar events.

Before completing enrollment or checkout, the initiator should verify every event’s date, time, duration, and time zone. Date validation does not confirm instructor, room, equipment, travel, or service availability; these must still be coordinated through the provider’s normal process.

What happens after successful enrollment or checkout

After the configured enrollment or checkout reaches confirmation, Eurekos performs the private-delivery setup.

Confirmation

The confirmation tells the initiator that enrollment was completed, a confirmation email was sent, and they can now invite others.

Standard enrollment emails are sent together with the Invite clients email used by the Reselling Gateway flow.

The confirmation may represent:

• A completed paid checkout
• A free enrollment
• A zero-value Transaction
• A centrally funded participation route
• The Eurekos part of a financial process completed elsewhere or later

Private clone

Eurekos creates a clone containing the original Activity Description title, features, and settings, except that Self enrollment is disabled.

The clone is therefore:

• Unavailable as a normal public or Storefront self-enrollment offer
• Available to invited users through the controlled invitation route
• Marked as a Reselling Gateway clone
• Linked by reference to its parent or original activity

Treat the clone as independent operational data after creation. Do not assume that later changes to the original will update existing clones.

Calendar events

For every Calendar event connected to the original activity, Eurekos creates a corresponding Calendar event in the private clone. Its reusable event content is carried into the new event, while its date, time, and time zone come from the values selected during enrollment or checkout.

This concerns Calendar events created in Calendar and connected to the Training Activity—not Event modules in the learning path.

Video-conference links are not carried into the private Calendar events. The provider or an authorized group lead must configure the correct private conferencing details before invitations and delivery.

Initiator and Transaction

The initiator is enrolled in the cloned activity and is shown only in that clone’s participant list. The associated Transaction is also transferred to the clone.

The Transaction may represent a monetary purchase or a zero-value enrollment. Review the amount, payment method, status, invoice information, and any external financial records before interpreting it as evidence of payment.

The initiator’s profile is marked as Contact Manager, and the initiator receives access to Invitations, where the private activity appears.

The Invitations list and invitation details do not provide the normal Preview training action for this private delivery. Do not treat its absence as a permission defect.

Original activity after initiation

The original Training Activity remains available in the Storefront and can be used repeatedly to start new private deliveries.

Each successfully completed Reselling Gateway initiation creates a separate private delivery:

Original reusable offer → Group A private delivery
Original reusable offer → Group B private delivery
Original reusable offer → Group C private delivery

Each private delivery has its own initiator, Transaction, dates, invitations, participants, and administration. Changes or activity in one delivery do not automatically affect the others.

This creates a one-template-to-many-deliveries model. Use stable customer references, organization relationships, and reporting conventions so administrators can distinguish private deliveries that share the same Activity Description title.

Group lead invitation flow

After the clone is created, the group lead opens Invitations and invites the intended participants.

Invitation emails include a See training link. The invitation is the controlled enrollment route into a clone whose Self enrollment is disabled.

Depending on the program design, invited participants may:

• Join without payment
• Complete their own payment
• Use an organization-funded route
• Follow an invoice or reimbursement process
• Participate under another approved funding arrangement

Existing authenticated invitee

An invited authenticated user opens the Activity Description, sees Enroll, and can proceed through the supported enrollment or checkout process even though Self enrollment is disabled on the clone.

Invited person without an account

The person opens the invitation and selects Enroll, then continues to login or account creation.

• If they register using the same email address that received an Email or File invitation, Eurekos recognizes the invitation and sends them to the appropriate enrollment or checkout route.
• If they register using a different email address, the invitation cannot be matched. They return to the Activity Description with Not available in storefront and cannot enroll through that route.

This matching protects the private invitation. Tell invitees to use the exact invited email address.

If a person without an account opens an invitation link that has already been used, Eurekos can show You don’t have permissions to access this page.

Person who was not invited

Someone who obtains the URL but was not invited reaches an unavailable Activity Description and cannot enroll.

The URL does not make the private clone public.

Contact Manager implications

The initiator becomes a Contact Manager when the private delivery is successfully created. This enables the invitation workflow, but it can also affect other active Promotions because Contact Managers are added to active Promotions.

Before broad use, decide whether an automatically assigned Contact Manager should receive unrelated active campaigns.

Review Promotion scope and lifecycle so a customer, partner, facilitator, or local group lead does not receive material intended for another audience.

The Contact Manager value remains a profile attribute after the immediate private-delivery setup unless an authorized administrator changes it through the approved process.

For more detail, see Introduction to Invitations and Promotions.

Optional group-lead editing of connected Calendar events

The platform option Allow to edit Events can permit the initiator, despite having the Participant role, to edit Calendar events connected to the Reselling Gateway activity they initiated.

The setting concerns connected Calendar events. It does not grant permission to edit Event modules or the wider learning-path structure. When Reselling Gateway is activated, confirm with Eurekos support whether group leads should receive this additional permission.

The available editing scope can include:

• Dates, times, time zone, and other details supported by the Calendar form
• Enable attendance marking
• Allow participants to cancel participation
• Video-conference settings

Enable this only when group leads are expected to coordinate their own private sessions. It gives a participant-role user operational influence over scheduling, attendance, cancellation, and conferencing for the connected Calendar events.

If it is disabled, internal administrators must complete those tasks.

In either case, document who owns:

• Final dates and time zone
• Instructor and location
• Private webinar creation and host access
• Invitations
• Attendance
• Participant cancellation
• Changes and notifications

Manager and Immediate Manager initiation

Manager and Immediate Manager users can start a Reselling Gateway activity only for themselves, not on behalf of another person.

After completing the process personally, they become the initiator in the clone and can invite others through the Contact Manager process.

Do not use a manager’s normal enroll-for-staff action to substitute another initiator into the Reselling Gateway flow.

This rule applies whether the activity is paid, free, centrally funded, or settled through another process.

Incomplete or cancelled enrollment or checkout

When an initiator starts the Reselling Gateway enrollment or checkout process, Eurekos can create a temporary private clone while the signup and selected configuration are being connected.

If the initiator completes the process, they become the first signup in the clone. The clone is then an active private delivery and is not considered empty or orphaned.

If the initiator leaves or cancels before their signup is connected:

• The intended enrollment or checkout is not completed.
• The initiator does not become an active participant in the private delivery.
• The temporary clone can remain without signups.
• The empty clone becomes eligible for scheduled cleanup after the configured period.

The presence of a temporary clone therefore does not prove that enrollment or payment was completed. Verify the initiator signup, Transaction status, and enrollment confirmation before treating it as an active private delivery.

If an invited participant later cancels their enrollment in an existing clone, that cancellation must not by itself delete the clone. The group lead’s delivery and any other signups continue to exist independently.

Automatic cleanup of empty clones

A scheduled cleanup process removes an empty clone only when all of the following conditions are true:

1. It was created through the Reselling Gateway flow.
2. It has no signups.
3. The configured period since clone creation has passed.

The cleanup check runs every 24 hours. This does not mean that every empty clone is removed exactly 24 hours after creation. The clone must first reach the configured age and then be identified by the next scheduled check.

This process removes abandoned private copies without affecting deliveries where the initiator or another participant has completed enrollment.

Do not rely on automatic cleanup to correct a clone that already contains valid signups or Transactions. Investigate and resolve those cases through the appropriate enrollment, support, or financial process.

Transactions and finance

Every enrollment produces a Transaction record, including free enrollment where applicable.

In Reselling Gateway, the initiator’s Transaction is transferred to the clone. The record may represent a paid purchase, a zero-value enrollment, or the platform-side record for a delivery funded or settled through another process.

Do not interpret the existence of a Transaction as proof of monetary collection. Use the Transaction amount, payment method, status, invoice information, and any applicable external financial records to determine how the delivery was funded.

When administrators cannot find the Transaction under the original:

1. Open the original Training Activity.
2. Identify its generated Reselling Gateway clone.
3. Open the clone’s participants and Transactions.
4. Search using Transaction, order, user, and provider references.
5. Confirm whether the enrollment or checkout reached confirmation.
6. Determine whether the Transaction is paid, zero-value, pending, invoiced, or associated with an external funding process.

Keep the relationship among the original, clone, initiator, signup, Transaction, and any payment-provider or external financial record in every reconciliation procedure.

Refund, cancellation, reimbursement, and correction decisions must consider both the financial and learning state.

Cancelling or refunding a payment does not automatically define what should happen to the private activity or its invited participants. Likewise, a free or externally funded delivery can still require cancellation and audit procedures.

Identify a Reselling Gateway clone and its original activity

A Training Activity created through Reselling Gateway is marked on its activity page with Reselling gateway, followed by the title of the original Training Activity.

The original activity title is a link. Select it to open the reusable activity from which the private delivery was created. This allows an administrator to review the source configuration or make changes intended for future private deliveries.

The original title can also be entered in the Activities list search. Because the original and its clones can share the same Activity Description title, the search may return several matching activities. Open an activity and check for the Reselling gateway marker and linked original title to confirm that it is a clone.

For a completed initiation, the clone can also be recognized by the following characteristics:

• Self enrollment is disabled.
• The initiator appears in the clone’s participant list.
• The initiator’s Transaction is connected to the clone.
• Additional participants enter through the controlled invitation route.

Treat the original and each clone as separate operational records. Changes to the original support future initiations but do not automatically update private deliveries that have already been created. Make changes directly to an existing clone only when they are intended for that specific group.

Change management for clones

After creation, treat every clone as a real group or customer delivery. In every aspect it is.

Before changing either the original or a clone, determine:

• Whether the change is for future initiations or one existing group
• Whether existing clones must be amended individually
• Whether participants or the group lead must be notified
• Whether dates, conferencing, capacity, certificates, automation, and completion remain valid
• Whether the funding or reimbursement model is affected
• Whether the change affects Transaction, contractual, accreditation, or regulatory evidence

Do not apply a change to private deliveries without reviewing participant progress and any commitments made to the affected groups.

Realistic use cases

Verify the configuration

Use representative accounts and the routes enabled for your delivery. Check the relevant outcomes before launch and after a material change; an administrator preview alone does not verify the participant experience.

Troubleshooting