A module can be used two ways: learners open it directly from its own link, or you copy it into a course so it becomes one lesson in a sequence. This page covers both, and what "copy" means for maintenance.
Share a module on its own
Every module has its own page in your classroom, with its own learners and analytics. Share the link when a single lesson is the whole assignment: a pre-reading before a workshop, a coding warm-up, a policy briefing that everyone completes once.
Because the module is not inside a course, nobody has to enrol in a course or find the right chapter. They open the link and start.
Copy a module into a course
- Open the module and choose Copy to Course.
- Pick the course from the list. You can search by title.
- The course curriculum appears. Click Insert here at the position you want, or Add as first lesson when the course is empty.
- Confirm. The lesson, including its quizzes, is copied into the course at that position.
You can copy the same module into as many courses as you like, and into the same course more than once.
What a copy is, and is not
The copy is a full lesson owned by the course. It does not reference the module.
| After copying | What happens |
|---|---|
| You edit the module | The course copy stays as it was |
| You edit the course copy | The module stays as it was |
| You delete the module | Course copies keep working |
| Learners complete the course copy | Progress counts for the course, not for the module |
This is deliberate. A course that was already published to a cohort does not change under them because someone updated the source module.
Keeping copies current
Because nothing syncs, decide how you will handle updates before you copy widely:
- Treat the module as the master. Make changes there first, then re-copy into courses that still need the new version and remove the old copy.
- Keep a short list of where it went. For compliance or policy lessons, note which courses carry a copy so an update does not miss one.
- Copy late. When a course is still being built, copy the module in as the last step so it carries the newest version.
Deciding what to make a module
A useful rule of thumb: if you can imagine the same lesson in three or more courses, or want to share it on its own, make it a module.
| Good module candidates | Better kept inside a course |
|---|---|
| Foundational concept explanations | Content that depends on the previous lesson |
| Company or school policy briefings | Exercises tuned to one cohort's level |
| Tool or platform how-tos | Introductions that reference course-specific context |
| Vocabulary and drill sets | Case studies tied to one program |
| Orientation and onboarding lessons | Exams and anything that needs course-level grading |