Remote SCORM allows you to connect the TinQwise learning platform to an external LMS. Learners stay in their familiar LMS while accessing platform-based content through a SCORM package.
What is Remote SCORM?
Remote SCORM (also known as proxy SCORM) lets you share content built in the platform inside another LMS. Instead of exporting static content, Remote SCORM launches the live platform experience inside an iframe—keeping the look, feel, and logic of your existing setup.
From a learner's perspective:
A learner clicks a course link in their LMS and is launched into the platform in an iframe. They land in the discovery stream and can access content from there.
How to link the platform to an external LMS using SCORM
Contact TinQwise
Ask for your domain to be added to the whitelist
Confirm that the SCORM feature is enabled on your platform
🔥 Without this, the SCORM file will not work correctly in the external LMS.
Go to Content > Integrations > Remote SCORM
Click Create Remote SCORM
Enter a title
Add groups
Choose which group of users will access this SCORM file, then save the settings. This creates the Remote SCORM automatically.
Download the ZIP file
Use Actions > Download zip to download your SCORM package (SCORM 2004 4th Edition).
Upload the zipfile to your external LMS
(Optional) View or edit SCORM details via Actions > Remote SCORM
(Optional) Remove SCORM via Actions > Remove Remote SCORM
Don’t forget to also delete the group and voucher attached to the SCORM in Groups and Vouchers (named after the SCORM title in step 4).
Content differentiation
Each Remote SCORM zip file appears in your LMS as one tile or activity. To offer different content for different audiences, create multiple Remote SCORM packages.
💡 Tip:
Create one package per journey to display unique tiles for each audience in your external LMS.
User identification
The platform collects the following user data (if available from your LMS):
User ID
First name
Last name
It does not collect:
Email addresses
Departments
Job roles
⚠️ If a user accesses multiple SCORM tiles, they may be treated as separate users in the platform.
All SCORM users are grouped under a parent group called Remote SCORM groups, with subgroups created for each SCORM package to help track user activity.
Progression and reporting
Remote SCORM has limited reporting:
Completion starts at 0% and remains incomplete until the learner reaches 100% progress.
Once completed, we send the completion status:
completed
If your LMS requires it, we also send a success status:
passed
💡 Tip:
If tracking is important to your organisation, consider using LTI instead of SCORM.
👀 Good to know
Each SCORM package is tied to a specific target group in the platform
Ensure your platform (groups, content, structure) is set up before creating SCORM packages
We support SCORM 2004 4th Edition
You can only land on the Discovery Stream, not specific modules
Max file size is 2 GB
Each package is one ZIP file. If your LMS blocks external sources, it may prevent content like images from loading
Extra setup tips for smooth implementation
Some third-party LMS systems have stricter network rules. If your SCORM package doesn’t load correctly, ask the external LMS team to whitelist the following domains:
Your platform URL
https://cdn.platform.co.nl
https://cdn.qollab.io
https://fonts.googleapis.com
https://*.content.qollap.com
https://cdn-cb.qollab.io