Skip to main content

⚙️ Distribute Your Didask Training on an External LMS via SCORM Connect

Connect your Didask training courses to any LMS to give your learners the full instructional experience from their usual environment.

Written by Océane

⏱️ The Essentials in 3 Minutes
​
• Your learners follow the training from their LMS, while keeping the full Didask experience.
• A simple export in a few clicks from the Publish button.


⚙️ Export Your Publication via SCORM Connect

  1. Create your publication

    1. If your project has no publications : Click Publish (top right of your project), then click > External LMS.

    2. If your project already has one or more publications : Click Publications (top right of your project), then click Create a new publication then > External LMS.

  2. If your project does not contain any modules with the "to publish" status, a page will appear on the screen allowing you to choose the modules you wish to distribute. You can choose to set all modules to "to publish" status or select only a portion from the drop-down list.

  3. Configure the distribution using the Content Unlocking, Experience Customization and Distribution Settings tabs.

  4. Then return to the Distribution Settings tab

  5. Choose the version to generate for your package (1.2 or 2004 3rd Edition or 2004 4th Edition)

  6. Paste the exact URL of your LMS in the dedicated field (if you deploy the same content on multiple LMSs: add as many URLs as necessary) The entry must start with "https://" and contain only the domain name, with no path or final "/".

  7. Choose the language(s) to include in your package

  8. Select the default language for your learners

  9. Once your publication is configured, click Publish

  10. Download your SCORM package using the dedicated button


📁 Understand What SCORM Connect Is

SCORM is a standard shared by most LMSs. A SCORM package is a .zip file used to transport training content from one tool to another.

SCORM Connect goes further: it links your LMS to Didask's servers via an iframe.

In practice, this means:

  • Your content stays hosted on Didask. Learners keep the full instructional experience: AI, positioning tests, corrected activities.

  • Your LMS receives the learner's identifier (learner_id, learner_name) and their learning data.

  • Detailed statistics (by module, by activity) remain on the Didask side, for your admins and authors.


⭐️ Benefits of SCORM Connect

Benefit

What it changes for you

Automatic availability

Your publication is accessible in your LMS, and usage data updates automatically.

Real-time updates

Your corrections are reflected immediately, without replacing the package.

Detailed instructional statistics*

On the Didask side, you keep more granular tracking than in your LMS.

Session resume

If the learner closes their session between two modules, already completed modules are saved.

Data reported back to your LMS:

  • The learner's score.

  • Time spent on the training.

  • Statuses: not started, in progress, completed, passed.

  • In case of a final assessment: the assessment score and pass/fail status (however, detailed answers to each question are not transmitted to the LMS - they remain viewable only in Didask statistics).

⚠️ Statistics do not include intermediate module progress.


📥 Choose the Right SCORM Version for Your LMS

Version

When to use it

SCORM 1.2

Recommended by default: the most universal.

SCORM 2004 (3rd edition)

If your LMS requires it or expects a weighted score.

SCORM 2004 (4th edition)

The most recent version, rarely used.

💡 Check in advance which version your LMS recommends.

⚠️ Important - score reporting differences by version:

  • If your LMS requires a normalized/weighted score (via the standard variable cmi.score.scaled), you must export your content in SCORM 2004.

  • SCORM 1.2 does not support this variable. If your LMS is configured to expect a scaled score but you exported in SCORM 1.2, scores will not report correctly.

Navigation and experience available in your SCORM export:

Single-SCO (embedded navigation)

Criterion

Single-SCO (embedded)

Navigation

Embedded Didask menu

Instructional experience

Complete: home page, chapters, positioning test

Completion and score

Calculated across the entire path

What is reported to the LMS

Overall publication score (0 to 100%)


📊 Statuses Reported to the LMS

Status

Meaning

Completed

The learner has gone through all the content but can still improve their score.

Passed (no assessment)

Path validated by simple consultation (no graded assessment).

Passed (with assessment)

Final score equal to or above the passing threshold.

Failed

Minimum score not reached and no more attempts available.

Passed (Multi-SCO)

Module or step validated in a multi-module path.


💡 Best Practices

  • Default version: SCORM 1.2.

  • Recommended browser for testing: Google Chrome.

  • To test your training as an learner, log out of Didask or open your LMS in a different browser, to avoid session conflicts.


❓ Frequently Asked Questions

How are users authenticated in Didask?

Via two fields transmitted by the LMS: a unique ID and an identifier (name or email depending on your LMS). By default, the learner_id appears in the admin. Display of first/last name can be enabled internally by Didask.

Do I need to re-export the SCORM Connect package after modifying content?

No, no re-export is needed - this is one of the main advantages of this distribution mode. Changes such as removing a module are reflected directly.

Are statistics preserved in case of a new export?

Yes, statistics are preserved on Didask. However, depending on your external LMS settings, data may not be retained there. On Didask, statistics will be updated, allowing you to track the impact of changes directly from the authoring tool. However, if content is removed, the corresponding statistics will no longer appear in the learner's profile.

If a disabled user tries to connect to a SCORM Connect via their LMS, will their account be automatically reactivated?

No, the user is not automatically reactivated. When an account is disabled, it is a manual action intended to voluntarily remove access. If the user tries to connect via their LMS, they will see a message indicating that access is not possible.

For the learner to access the content again, the admin must first manually reactivate the account.

If the account was deleted rather than disabled, the learner can reconnect via another package, which creates a new account.

I see an "Oops, access denied" error on my external LMS - what should I do?

Oups... Accès refusé https://....... is not authorized as lmsOrigin

Solution: Check whether the URL entered in your publication (on the Didask side) matches the exact URL of your LMS.

  • If the URL does not match your LMS URL: Edit it and add the correct URL before testing again. Note: for optimal navigation, we recommend closing the Didask tab before opening your LMS platform. Alternatively, use two different browsers (e.g. Chrome and Firefox) to keep both sessions active without conflict.

  • If the URL does match your LMS URL: contact us via the Help button at the bottom right of your Didask platform.

I see an error message with the cause "User 'XX' is disabled" - what should I do?

This message means the user in question has been disabled on your Didask account. To find them, copy and paste the identifier from the error message into Didask and reactivate the user.

What is the Learner_id and who generates it?

The learner_id is a unique identifier transmitted by your LMS to Didask at each session. Didask does not generate this identifier and cannot modify it: we simply check whether it is already known in our system. The exact mapping of this field depends on your distribution tool - contact your LMS provider to understand how it is generated.

Is the Learner_id reliable for credit calculation?

Yes. The rule is simple: 1 training launched for a learner = 1 credit, regardless of the number of sessions or visits. If the same learner_id accesses the same publication multiple times, even months apart, only one credit is counted.

💡 You have real-time access to the number of credits consumed directly from the platform, under the Licenses section.

What happens if the same user generates two different Learner_ids?

On Didask's side, two distinct learner_id values correspond to two distinct users, even if it is the same person in your organization. This can happen if your LMS generates a new identifier under certain conditions (session reset, parameter change, etc.). In that case, two credits would be consumed. If you notice this type of anomaly, contact your technical team or LMS provider to identify the cause.


Keywords: SCORM, SCORM Connect, SCORM package, external LMS, export training, LMS distribution, iframe SCORM, scaled score, SCORM 1.2, SCORM 2004, publish, distribute, publication, distribution.

Did this answer your question?