A remote content package is a .zip file that lets your module run on an external LMS while pulling content directly from the Skillcast LMS. This means updates you publish in Skillcast automatically appear on the external LMS without needing to export a new package. If you need to create or re-export a remote package yourself, follow the steps below.
You can find information about deployed packages in the article Export a content package, and the differences between deployed and remote packages in E-learning standards and features.
How to Export a Remote Content Package
Find the editable module you want to export. (Only editable modules can be exported.)
Select the Export a remote content package link on the right side of the module page.
At the top of the screen, you will see the export settings for your package.
Below the settings, you will find:
Remote content package usage – lists all user domains that have exported this module, the number of active users, and last access date.
History of exported remote content packages – shows previous exports, who exported them, and their settings.
Select Export remote content page once you have selected your required settings.
If exporting again using the same user domain, ensure you are not actively using an existing package unless you have lost it or Skillcast has released technical improvements. Exporting again in the same domain can cause duplicate reporting or additional seat usage in your LMS.
If the package will be used on another LMS, set up a separate user domain before exporting. This helps distinguish reporting between systems.
Settings
Below is a table of all available export settings. Test your package with your Customer Success Manager before assigning it to employees.
Setting | Description |
Package type | Select the version required by the third‑party LMS. Options include: SCORM 2004 4th Edition, SCORM 2004 3rd Edition, SCORM 2004 2nd Edition, SCORM 1.2, xAPI. |
User Domain | Choose the staff domain the module will be tracked in. Use the same domain when re‑exporting to avoid duplicate subscription usage. Contact [email protected] if unsure. |
Export type | Choose to download the package locally or upload it to File Exchange (FE). If uploading to FE, select the domain the recipient can access. |
Duration | Set the course length. Approximate formula: number of words ÷ 150 = minutes. |
Show advanced settings | Reveal additional SCORM‑only settings. (Hidden for xAPI package type.) |
Escape special characters in suspend data | Prevents LMS errors caused by unsupported characters. Leave unticked unless required. |
Use minimal meta data in manifest | Generates a simplified manifest for LMSs with limited SCORM support. Leave unticked unless required. |
Specify primary objective in manifest (SCORM 2004 only) | Works with roll‑up rule settings to define completion behaviour. |
Specify roll‑up rules in manifest (SCORM 2004 only) | Forces LMS completion handling based on content behaviour. |
Conclusion
You now have an overview of how to export a remote content package, what each setting does, and when to use separate user domains. If you are unsure at any stage, always check with your Customer Success Manager before assigning content to learners. For further support, contact your Customer Success Manager by selecting Send us a message via the help icon on your portal, or by emailing [email protected].