Configuring launch from your LMS

Your LMS remains the entry point: it hosts a SCORM package exported from Beedeez, the learner clicks it, arrives in Beedeez already signed in, and the result is written back to the LMS. This article describes that journey and the settings that govern it. The package itself is covered in SCORM export, from the LMS angle.

⚠️ Prerequisite: the LMS option must be enabled on your account. Without it, the LMS sub-page does not appear under Configuration > Integrations.

Where the configuration is set

Open Configuration > Integrations > LMS. The sub-page stacks four blocks: LMS, CROSSKNOWLEDGE (displayed only when the corresponding account option is enabled), WBT and LRS.

In the LMS block:

1. Click Setup default LMS. A dialog opens with seven fields: Name, Base URL, Authentication type, Login, Password, Method name and User Id.
2. Select a value in Name. Eight values are available, displayed in capitals: WBT, CROSSKNOWLEDGE, CORNERSTONE, TALENTSOFT, SYFADIS, SUCCESSFACTORS, DOKEOS, MOODLE. The last four display the message “For this integration, please contact your support team who will help you to correctly configure the selected LMS.”
3. Fill in the connection fields. Authentication type offers a single value, BASIC.
4. Click Add other LMS to create an additional configuration. Additional configurations are then listed under Available Configurations.

🔧 These seven fields describe a SOAP call to your LMS. The call is used as soon as a Base URL is filled in. The rest of the launch, including the allowed domains and the SSO fallback, has no screen: it is set up with support.

How the learner is recognised

When the learner clicks the package, the launcher reads the learner identifier and the display name from your LMS, adds the launch data provided by the LMS and the token generated at export time, then calls Beedeez. No email address, group, department or academy is transmitted.

Beedeez then looks for an account carrying that learner identifier, for that Beedeez account. This is the only matching key: neither the email address nor the login is used, unlike the provisioning described in Which brick for which need.

• If an account is found, the learner is signed in.
• If no account is found and the SOAP call above is configured, your LMS is queried. The launch fails when your LMS does not know that identifier.
• If no account is found and no SOAP call is configured, an account is created immediately, without an email address.
• When an SSO fallback is configured, the launcher displays Authentication in progress and a Login link, then opens a sign-in window. The sign-in must be completed within fifteen minutes.

⚠️ Account creation cannot be disabled from this page. An unknown identifier produces an account, never a refusal. Align your identifiers before opening the launch: the same person arriving through the LMS and then through your HR system ends up with two accounts and two separate histories.

What is written back to the LMS

During the session, the page open in the browser writes the status, the score scaled to 100 and the time spent into your LMS. The status remains “in progress” until the content is finished, then becomes “passed” or “failed”. A capsule is finished at 100%, and a track is finished once every capsule is finished or the track is passed.

⚠️ The learner’s browser performs this write. Beedeez does not send the value again afterwards. If the learner closes the tab too early, your LMS keeps the previous value while the capsule is finished in Beedeez, and the two sets of figures diverge.

What the launch does not cover

• It does not open the mobile application and carries no academy. The content is loaded in the browser, inside your LMS’s SCORM player, without offline mode.
• It does not extend permissions. It grants access to the exported content only. Beyond that content, the learner sees what their groups allow.
• The LMS Config selector in the export dialog does not select the configuration applied at launch. The domain the click comes from does.
• Enable SCORM API injection during processing applies to a SCORM module imported into a capsule, which is the opposite direction.

Points to check before opening the launch

Name labels the configuration. It does not select a connector: the identification mode applied at launch is a separate server-side setting, and the call to your LMS depends on a Base URL being present, not on the value selected. The blocks that do change the behaviour are covered in Dedicated connectors.

The package acts as a key. It opens access without any further authentication, and it keeps working after someone leaves the company. No screen revokes it afterwards. Your only control is the date set by ticking Enable exported SCORM package expiration at export time, a box that is unticked by default. Keep the file inside the LMS and do not circulate it further.

Deactivating a learner does not close the door. By default, a launch reactivates a deactivated account. A server-side setting can prevent this reactivation, and it is not available on this page. To remove access, remove the content from the LMS.

Two error messages exist. “Your access authorization to this SCORM package has expired” indicates an expired package. “An error occurred while loading your SCORM package” covers everything else, from an unknown identifier to an unpublished capsule. Run your acceptance test with a real learner account.

Going further

• SCORM export, from the LMS angle: the package to upload, its version and its expiry date.
• xAPI and LRS: this page is its prerequisite, since a statement is only emitted for a learner recognised through an LMS launch.
• Dedicated connectors: the CROSSKNOWLEDGE and WBT blocks, and what they add.
• Which brick for which need: aligning identifiers before opening the launch.