Delivering your Beedeez content to an external LMS
Your learners already work inside an external LMS and you want your Beedeez content to reach them there. Two routes lead out of Beedeez, and one reporting channel can be added on top of the second. This page tells you which one to read, and what each one costs you before you commit to it.
Delivering your Beedeez content to an external LMS
Your learners already work inside an external LMS and you want your Beedeez content to reach them there. Two routes lead out of Beedeez, and one reporting channel can be added on top of the second. This page tells you which one to read, and what each one costs you before you commit to it.
⚠️ Prerequisites: the LMS option on your account. Without it, neither the Scorm option of the Share dialog nor the LMS sub-page under Configuration > Integrations appears. Exporting a SCORM package also requires the diffusion right Authorized to generate SCORM exports from capsules and tracks, and the CROSSKNOWLEDGE block requires a further option of its own. These are separate switches: holding one does not give you the others.
ℹ️ These pages cover your Beedeez content going out. To play a SCORM module, a video or a web page inside a Beedeez capsule, read Enriching your capsules with external content instead. That is the most common wrong turn onto this section.
Choosing between the two routes
You hand the LMS a file. You produce a SCORM package, the LMS imports it and treats it like any of its own modules. The LMS is what records the result.
The LMS opens Beedeez. Nothing is deposited: the LMS holds a link, the learner clicks, lands in Beedeez already authenticated, and the result goes back to the LMS. This route takes configuration on both sides.
Whichever you pick, Beedeez is what serves the content. An exported SCORM package carries a launcher rather than the notions themselves: when the learner opens it, it fetches the capsule from Beedeez. A capsule you correct stays correct in the LMS, and a capsule you take offline stops opening there.
Handing the LMS a SCORM package
- Exporting a capsule or a track as SCORM: the manual gesture, from the Share dialog. Take this one for a handful of contents, or for a first trial.
- Scheduling automatic SCORM package delivery to an SFTP: a scheduled job builds the packages and drops them on its own. Take this one once the manual export repeats, and only if your LMS can consume an SFTP drop.
Having the LMS open Beedeez
- Configuring launch from your LMS: authentication first, tracking second. Take this one when the LMS stays the official entry point.
- LMS-specific connectors: CrossKnowledge, WBT, TalentSoft, Cornerstone: what each of these four platforms actually adds. Read it before raising the subject with your support team, because none of these connectors is self-service.
Reporting more than completion to an LRS
Sending xAPI statements to your LRS applies when you already run an LRS. It is neither one more delivery route nor an independent analytics channel: nothing is emitted until launch from your LMS is in place.
Deciding which figures are authoritative
Whichever route you take, the LMS figures and the Beedeez figures will not match. Each side counts what it sees go past, and the two do not observe the same events. Decide before you open the route which of the two is your reference, so that a gap found months later does not turn into an investigation.
When an integration does not behave as expected
Start with Common problems: integrations, which covers the symptoms shared by these routes before you go through your support team.