How eLearning Works

The learning module runs standards-based e-learning: you upload course content, assign it to people, and it records what they did.

Where to find it

Architect Panel → eLearning:

• Courses & Assignments — the course console — courses, units, assignments
• Learner Records — a learner’s registration against a package
• Course Attempts — each attempt at a package
• Course Sessions — individual launches
• Learning Objectives — objective-level results

The layers

1. A package is content you upload — a SCORM, xAPI or cmi5 package produced by an authoring tool.
2. A course is what a learner is assigned. It contains one or more units, each of which is a package or a link.
3. An assignment says who should do a course, by when, and how often it repeats.
4. An enrolment is one learner on one course for one cycle.
5. A registration is that learner against one package, holding the score and status.
6. Attempts, sessions, interactions and objectives are the detail underneath.

The distinction between a course and a package is the one to hold on to. A course is yours; a package is the content.

Why a course is more than a package

A course can combine several packages with a reading link and a document, in a defined order, with a rule about what counts as complete. A single package cannot express any of that.

Even for one piece of content, wrapping it in a course gives you versioning, expiry, certificates and assignment — none of which a bare package has.

Results are recorded, not asserted

The platform records what the content reports: score, completion, success, time, and where the learner got to. It does not decide those things — the package does, and the package was built by whoever made it.

That distinction matters for anything you are relying on for compliance.

Detail down to the question

Where a package reports it, individual interactions and objectives are stored — the question, the learner’s answer, the correct answer, whether it was right, and how long it took.

Most organisations never look at this, and it is the most useful data in the module.

What it does not do

Sequencing inside a package remains the package’s job. The platform sequences units within a course; it does not implement IMS Simple Sequencing or cmi5 block sequencing.

Start with one course

Upload one package, build a course around it, assign it to yourself, complete it, and look at the record. That hour teaches more than any amount of configuration planning.

Worked example

An organisation runs annual information-security training as one course with three units — a SCORM module, a policy document and an assessment package — completed in order, valid for twelve months, assigned to everybody with a thirty-day due window.

Recommendations

• Wrap even a single package in a course for versioning and expiry.
• Remember results come from the content, not the platform.
• Look at the interaction detail — it is the best data here.
• Run one course end to end before designing a programme.