How it works
Upload the package,
and it is a course
Drop in the zip you already own. It is unpacked, served and tracked, and it sits in the same catalogue as the courses that ship with the platform.
- Completion, score, time and pass or fail come back from the package itself
- Bookmarking, so a learner resumes where they stopped rather than restarting
- One catalogue, not a library and a separate list of imports
- Nothing charged per course, per conversion or per upload
- Your packages stay yours, and can be taken to another platform
Before you ask
What people check first
Will courses built in Storyline or Captivate run?
Yes, if they are published as SCORM 1.2, SCORM 2004, xAPI or cmi5, which is the normal output of both. The authoring tool does not matter; the publish format does.
What if a package is very large?
Every plan carries a storage allowance and larger blocks can be added on Grow and above. The allowance is enforced rather than silently exceeded, so you are never billed for an overage you did not agree to.
Do you support xAPI statements from outside the platform?
Yes. There is an xAPI endpoint, so activity recorded elsewhere can be sent in and reported alongside everything else.
Is cmi5 really supported, or just claimed?
Really. cmi5 packages are imported, launched with a session, and their statements are recorded and reported. It is the newest of the four and the one most often listed and not implemented, which is why it is named separately.