To use our SCORM packages in a third party LMS there are some requirements that must be met.
These are as follows:
Secure Access via HTTPS:
- Your third-party LMS must be accessed through HTTPS. The iHasco Atlas LMS uses the secure HTTPS protocol, and any shared content must follow the same standard.
- To check, sign in to your LMS and look for a padlock icon in the browser's address bar.
- If you have a self-hosted LMS (e.g., Moodle), speak with your developer about switching to HTTPS if it’s not already enabled.
Domain Access:
- Learners must have access to iHasco domains and those associated with our video CDN.
For more details, refer to our Domain inclusion list.
- Learners must have access to iHasco domains and those associated with our video CDN.
JavaScript:
- Learners' browsers must have JavaScript enabled.
Third-Party Cookies:
- Learners' browsers must allow third-party cookies, and the Prevent Cross-Site Tracking setting must be disabled.
SCORM File Compatibility:
- Your third-party LMS must support SCORM version 1.2 or 2004 files.
Ensuring these settings are in place will help prevent playback or access issues for learners.
Note All of the features native to the iHasco Atlas LMS, for example, reminder emails and certificates, are disabled for training sessions via a third party LMS.
To learn more about SCORM packages, see How to download a SCORM package.
To learn more about our featured LMS providers, see SCORM Compliant eLearning & integration options
To learn more about how iHasco processes personal data in relation to SCORM packages, see How iHasco process personal data in relation to SCORM packages
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article