LMS packages
An LMS package adds a demo or a training course to another learning management system (LMS), such as Moodle, Cornerstone or Docebo. The package only launches the lesson: lessons play from Demo-Creator, and the LMS records completion, score and where the learner stopped.
- For a demo, download it from Share & export → Export. It becomes one lesson.
- For a training course, owners and admins download it from the course's Sharing tab. It holds one lesson per published demo, in course order.
Choose a standard
| Standard | Choose it when |
|---|---|
| SCORM 1.2 | You are unsure: nearly every LMS accepts it. |
| SCORM 2004 (4th edition) | Your LMS supports it. It reports progress within a lesson and exact scores. |
| cmi5 (xAPI) | Your LMS supports cmi5 and you want the results as xAPI statements in its records. |
What the LMS receives
- Completion, when the learner reaches the end of a lesson.
- For a lesson with a quiz: the score, and passed or failed at the pass mark. The pass mark is 80% for a demo package and the course pass mark for a course package; many LMSs let you change it.
- The current step, so the lesson resumes where the learner stopped, and the time spent.
Answers you grade by hand never reach the LMS, so such lessons report completion without a score. Use automatically graded questions in lessons you deliver through an LMS.
Updates and limits
- Republishing a demo updates it in every LMS that uses the package. Download a new package after adding or removing course lessons or changing the course pass mark.
- Unpublishing or deleting a demo stops it in the LMS.
- Results stay in the LMS. Learners are not signed in to Demo-Creator, so their plays count as anonymous views in Analytics, and they do not appear in a course's Results.
- A protected demo asks LMS learners for access as its link does; see Access protection.
- Learners must be able to reach Demo-Creator from where they use the LMS. If your organization has a custom domain, packages use it.