- View
Turn a learning plan into a course connection
A training team wants employees to complete Data Foundations before moving into Reporting Essentials. The two Moodle courses already exist, but a link between their pages does not create an automatic learning path. Moodle needs a rule that connects completion of the first course to enrollment in the second.
This lesson uses the Course completed enrollment plugin, identified technically as enrol_coursecompleted. A plugin is an extension that adds functions to Moodle. The steps assume that your organization uses this plugin; other enrollment plugins may use different settings and rules.
By the end of this lesson, you will understand how to prepare the plugin, identify the correct course direction, and save the connection. The focus is the setup itself, not when enrollment happens or whether a learner can enter the destination course.
Separate the completion signal from the enrollment action
When an employee completes Data Foundations, that course provides the completion signal. The enrollment method in Reporting Essentials uses that signal to enroll the employee in the destination course. Enrollment means adding a user to a course with a role, such as Student.

An enrollment method is a rule or process that adds users to a course. With this plugin, the method belongs in the course that receives the learner, not the course the learner finishes. Think of Reporting Essentials as a doorway: its enrollment method names the completed course that allows the learner through.
| Connection detail | Course A: Data Foundations | Course B: Reporting Essentials |
|---|---|---|
| Purpose | Provides the completion signal | Receives the learner |
| Configuration needed | Valid course completion conditions | Course completed enrollment method |
| Place in the path | Source course | Destination course |
| Expected learner role | Student completing the course | Student enrolled through the plugin |
This connection creates one step in an adaptive learning path, a route that changes according to learner progress or results. Here, the rule responds to course completion rather than making a separate decision about each quiz score. If a score should determine progression, Course A’s completion conditions must reflect that requirement where supported.
Prepare the plugin at the site level
Before a course creator can add the connection, a Moodle administrator must make the enrollment plugin available. Installing a plugin adds its code to the site; enabling it allows Moodle to use it. These are separate actions, so an installed plugin may still be unavailable in the course’s enrollment menu.
The administrator should confirm that the plugin release supports the site’s Moodle version and meets local security requirements. Use the Moodle plugins directory or the organization’s approved installation process rather than an unknown download. For this example, the request should name enrol_coursecompleted and explain that Reporting Essentials must accept learners who complete Data Foundations.
- Identify the plugin: Give the administrator the name Course completed enrollment and component name
enrol_coursecompleted; the output is a clear installation request. - Check compatibility: The administrator checks the plugin release against the site’s Moodle version; the output is an approved release.
- Install through the approved process: The administrator completes the installation and any required upgrade steps; the output is an installed plugin.
- Enable the enrollment method: The administrator opens Site administration → Plugins → Enrollments → Manage enrollment plugins and enables it; the output is an available enrollment method.
- Confirm course-level permissions: The administrator checks that the course creator can manage enrollment methods in Reporting Essentials; the output is an account ready to configure the connection.
Menu names can vary with Moodle versions, language packs, and themes. A missing option does not always mean that installation failed: the plugin may be disabled, or your account may lack permission. Ask the administrator to check those points before requesting another installation.
Give Course A a meaningful completion signal
The plugin needs a course completion record, not simply evidence that a learner opened Course A. Course completion is Moodle’s record that a learner has met the course’s defined requirements. Those requirements must match the learning decision you want to make, or the connection may advance learners on the wrong basis.
For Data Foundations, the training team requires a passing result on the final knowledge check. The creator configures the activity’s passing requirement and completion settings, then includes that activity in the course completion conditions. A score such as 80% is an instructional choice in this example, not a fixed requirement of the enrollment plugin.
- Confirm completion tracking: Check that completion tracking is enabled for the site and Data Foundations; the output is a course that can record completion.
- Define the required activity result: Configure the final knowledge check with an 80% passing grade and completion that requires a pass; the output is a clear activity-level requirement.
- Set course completion conditions: Include that activity in Data Foundations’ course completion requirements; the output is a course-level completion rule.
- Review the full condition set: Check whether other required conditions also apply; the output is a completion rule that matches the intended learning standard.
A common misconception is that passing any quiz automatically completes the course. Moodle distinguishes activity completion, which records progress in one activity, from the overall course completion record. If the final knowledge check is not part of the course completion conditions, its passing result alone does not establish the intended course-level signal.
Add the connection inside Course B
Put the Connection in the Destination
The key configuration happens in Reporting Essentials, the destination course. Its enrollment method identifies Data Foundations as the source course whose completion is required. This direction matters: adding the method inside Data Foundations would not create the intended route into Reporting Essentials.
The exact field labels depend on the installed plugin release. In the steps below, source course means the field used to select the course learners must complete. Confirm the field’s help text if the interface uses a different label, and use the plugin’s documentation for release-specific options.
- Open the destination: Enter Reporting Essentials and open Participants → Enrollment methods; the output is Course B’s enrollment-method list.
- Add the method: Select Course completed enrollment from the available methods; the output is a new configuration form.
- Select the source: Choose Data Foundations as the course learners must complete; the output is a connection from Course A to Course B.
- Set the basic enrollment details: Ensure the method is enabled and select the intended learner role, normally Student, where the setting is available; the output is a usable enrollment rule.
- Save and review: Save the form, then reopen the method to confirm the source course and status; the output is a saved, verified configuration.
Saving the connection is not proof that a learner has been enrolled. It confirms that the rule exists in the destination course. Keep configuration review separate from checking learner outcomes, and avoid changing unrelated enrollment methods while setting up this connection.
Example: prepare the employee reporting pathway
The training team uses Data Foundations as the entry point for its reporting program. Employees must pass the final knowledge check at 80% before progressing to Reporting Essentials. Both courses are already available on the same Moodle site, and the administrator has approved the plugin.
- Check the source requirement: The creator confirms that Data Foundations requires a passing final knowledge check; the output is the intended completion signal.
- Open the destination settings: The creator opens Reporting Essentials’ enrollment methods; the output is the correct location for the rule.
- Create the connection: The creator adds Course completed enrollment, selects Data Foundations, and saves the enabled method; the output is the configured pathway.
- Record the setup: The creator notes the source course, destination course, and method used in the team’s course documentation; the output is a connection another team member can maintain.
This setup supports a repeatable training workflow without requiring a separate manual enrollment decision for every learner. Its limit is equally important: the plugin acts on the configured completion requirement, not on a separate judgment of job readiness. The course team remains responsible for making the completion standard meaningful.
Example: correct a connection placed in the wrong course
During a setup review, a second course creator finds the method inside Data Foundations with Reporting Essentials selected as the source. The course names look correct, but their positions are reversed. That configuration describes enrollment into Data Foundations after completion of Reporting Essentials, which is not the intended path.
| Review point | Incorrect setup | Correct setup |
|---|---|---|
| Method location | Data Foundations | Reporting Essentials |
| Selected source course | Reporting Essentials | Data Foundations |
| Direction described | Reporting Essentials → Data Foundations | Data Foundations → Reporting Essentials |
- Identify the reversed rule: Review the method’s location and selected source; the output is a confirmed configuration error.
- Stop the unintended rule: Disable the incorrect method while its use is reviewed; the output is an inactive reversed connection.
- Create the intended rule: Add the method inside Reporting Essentials and select Data Foundations; the output is the correct direction.
- Verify the saved details: Reopen the new method and confirm its source, role, and enabled status; the output is a reviewed connection.
This review prevents a configuration error from becoming part of the organization’s training process. On a live course, do not delete an existing enrollment method without checking whether it manages current enrollments. Changing the rule also does not, by itself, confirm or repair any learner enrollments already created.
A connection you can verify
A reliable connection has three parts: an available plugin, a meaningful completion signal in Course A, and an enrollment method in Course B. The destination course holds the rule, while the source course supplies the required completion. Keeping those responsibilities clear makes the setup easier to review and maintain.
Before treating the configuration as ready, confirm these points:
-
Plugin: Course completed enrollment is installed, enabled, and available to the course creator.
-
Source: Data Foundations has the intended course completion conditions.
-
Destination: Reporting Essentials contains the enrollment method.
-
Direction: The saved method selects Data Foundations as its source.
-
Status: The method is enabled and uses the intended learner role.
Next, we'll build on this by exploring Check Enrollment Timing and Course Access.