Self-enrollment Eligibility and Requirements - Article

What self-enrollment eligibility helps you achieve

Self enrollment transfers the enrollment choice to the participant. Eligibility requirements keep that choice within the rules of the training program.

Use them when a participant must qualify before receiving a signup, for example:

• Complete foundation learning before registering for an advanced workshop.
• Hold a valid certificate or Skill before booking an assessment.
• Attend an orientation Event before entering practical training.
• Belong to an approved organization or job function.
• Wait until enrollment opens on a defined date.
• Complete one required declaration or questionnaire during enrollment.
• Already be registered for another activity in the same program.

The participant can normally see the Activity Description and understand what is missing. Eurekos prevents self-enrollment until the requirements are satisfied.

Eligibility controls entry—not learning sequence

After enrollment, these requirements have finished their job. If a participant should enroll now but remain unable to open the complete activity or a later module, use Access Restrictions instead.

Understand the complete self-enrollment design

Enabling Self enrollment is only one part of making a Training Activity available.

Review:

• Storefront activation for registered and, where intended, anonymous users
• Storefront sections, categories, and audience targeting
• Activity and module availability
• Organization visibility
• Latest registration
• Seats and waiting-list behavior
• Eligibility requirements
• Participation Approval
• Price, currency, tax, and payment methods
• Activity Description and enrollment-button presentation
• Confirmation and follow-up communication

A free activity with no prerequisites is simple. A public paid activity with organization targeting, limited seats, approval, and prerequisites is a complete business process and should be tested as such.

Confirm platform prerequisites

The activity-level Self enrollment feature is available when Storefront is enabled in the platform's General settings.

Two platform controls can further align discovery and enrollment with Storefront audience rules:

• Filter catalog trainings by Storefront visibility limits discovery to training intentionally visible to the user.
• Block enrollment by Storefront visibility also prevents direct-link enrollment when the activity is outside that user's visible Storefront. Contact Eurekos support for changes to this configuration.

The first control affects what users find. The second closes the direct-link path as well.

If direct links should remain usable for a controlled audience even when an activity is not shown in their normal catalog, do not enable the blocking behavior without testing that use case. If Storefront targeting is a security or contractual boundary, enable both appropriate discovery and enrollment enforcement rather than relying on a hidden card alone.

For more detail, see Setting up the Storefront, Activity Description.

Choose the correct control

Avoid expressing the same business rule at several layers without a reason. Requiring the same certificate for Storefront targeting, self-enrollment, activity access, and certificate issuance can create a journey that is difficult to explain and support.

Configure self-enrollment requirements

1. Open Course Administration → Activities.
2. Open the Training Activity and edit it.
3. Add or enable Self enrollment at activity level.
4. Enable Restrict self enrollment until the criteria are met.
5. Add the required criterion.
6. Add further criteria where needed.
7. Configure AND/OR logic deliberately.
8. Save the activity.
9. Review the Activity Description as an eligible authenticated user, an ineligible authenticated user, and—if the Storefront is public—an anonymous visitor.
10. Complete each prerequisite and verify that the action changes to Enroll at the intended time.

Use stable prerequisite records with clear ownership. Removing, replacing, expiring, or restricting the prerequisite can leave the target activity impossible to enter.

Understand AND and OR logic

For a mixed rule, write the intended logic in plain language before configuring it:

The participant must complete the foundation Course and either attend one orientation Event or already hold the equivalency certificate.

Then test every valid and invalid branch. Do not rely on visual placement alone to confirm grouping.

Choose the correct criterion

Each criterion evaluates existing evidence or profile data. It does not create the prerequisite enrollment, repair missing evidence, or explain a business exception automatically.

Understand the authenticated participant experience

When an authenticated user does not meet every required criterion:

• They can open the Activity Description if other visibility controls permit it.
• The primary action is See requirements.
• Selecting it opens Enrollment requirements.
• The popup lists currently missing criteria.
• A requirement already satisfied is removed from the missing list.
• Available requirement links can take the user to the relevant Course, activity, Event, or other destination.

When all ordinary criteria are satisfied, See requirements changes to Enroll, subject to approval, price, seats, dates, and other enrollment controls.

When the only remaining criterion is Complete questionnaire, Enroll opens that questionnaire and the participant can continue after submission.

Make every requirement actionable

The popup should help the participant make progress. Before launch, confirm:

• The prerequisite is visible or reachable.
• The participant can enroll in it where necessary.
• Links open the intended record.
• Dates and schedules allow completion before Latest registration.
• Assessment and attendance can be recorded in time.
• The wording on the Activity Description explains why the prerequisite matters.

If a requirement such as Pass test is not clickable, the participant may lack enrollment in the activity containing the test. Repair the prerequisite route rather than expecting the user to discover it unaided.

Understand anonymous visitor behavior

When an activity is visible to unregistered visitors and has at least one self-enrollment requirement, the anonymous visitor sees a generic message explaining that self-enrollment may require certain conditions. Enroll sends the visitor to login or registration so Eurekos can evaluate their identity and evidence.

The anonymous message:

• Is the same for one or several criteria.
• Does not expose the criterion type or AND/OR structure.
• Is removed after login or account registration.
• Is replaced by the ordinary authenticated result: Enroll when eligible or See requirements when not.

If Storefront visibility also blocks the activity for the authenticated user, the person sees the applicable not-available or requirements message rather than a route that bypasses audience targeting.

Do not promise eligibility to an anonymous visitor. Eurekos cannot evaluate their profile, learning history, certificates, Skills, attendance, assignments, or signups until an identity exists.

Understand manager enrollment behavior

Managers, Partners, and Immediate Managers can see enrollment actions according to their role and relationship. The visible button does not make the selected staff eligible.

For direct manager enrollment:

• The manager can reach the Enroll flow.
• Each selected person's requirements are evaluated.
• If selected users do not meet the criteria, the enrollment fails and the popup lists the ineligible people.
• The manager does not bypass the prerequisite simply because they personally qualify or hold a management role.

For the separate manager request-for-others flow used with Participation Approval:

• The list can display a Requirements column.
• Ineligible people are greyed out and lack the individual request action.
• If included in a bulk request selection, they are skipped and the skipped quantity is reported.

Test the exact route being used. Direct enrollment can reject the selected operation, while bulk approval-request creation can skip ineligible records.

Coordinate requirements with Participation Approval

Eligibility and approval answer different questions:

• Eligibility: Does the participant satisfy the predefined conditions?
• Approval: Does the selected decision-maker authorize this application?

Both can be enabled. The person must satisfy eligibility before the request can proceed, and the approver must then make the admission decision.

Do not duplicate the same questionnaire as both a Complete questionnaire criterion and an approval-stage questionnaire without an explicit reason. Decide whether the response qualifies the participant automatically or supplies information for a human decision.

Coordinate requirements with Seats and Waiting list

Meeting every eligibility criterion does not guarantee a seat.

After the participant becomes eligible:

• Available capacity can allow registration.
• A full activity can offer Waiting list when enabled.
• A full organization allocation can waitlist the person while other organizations retain capacity.
• Latest registration can still close the route.

Likewise, a person on the waiting list may later become ineligible because profile data, certificate validity, or another condition changed. Test automatic promotion with the actual eligibility design.

Coordinate requirements with paid enrollment

Eligibility does not waive price or payment.

An eligible participant can still need to:

• Select a currency or payment method
• Supply billing information
• Apply an organization discount or Coupon
• Purchase Additional Products
• Complete payment or invoice processing

Coupons and prices do not bypass requirements. Keep the Activity Description clear about both qualification and cost.

Change requirements on a live activity

Before adding, removing, or changing a criterion:

1. Identify current participants, applicants, waitlisted people, and intended future audiences.
2. Determine who currently satisfies the old and new rule.
3. Confirm prerequisite access and timing.
4. Review linked, repeated, and nested activities.
5. Check automated communication and participant-facing explanations.
6. Test a newly eligible, newly ineligible, and already enrolled person.
7. Record the business decision and effective date.

Changing pre-enrollment eligibility does not remove an existing signup. If current participants should lose access, that is a separate and more consequential decision involving cancellation, Access Restrictions, or Access Expiration.

Practical configuration patterns

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