Admin / Editor · Allow about 15 minutes
Before you begin
Owner, Admin, or Editor with article access and SCORM available on your plan. Obtain a SCORM 1.2 or SCORM 2004 ZIP, no larger than 50 MB, with imsmanifest.xml at the ZIP root. Use a test article and a signed-in test learner before sharing widely.
1. Add the package to an article
Open the article editor and place the cursor where the activity belongs. Open the block insertion menu and choose SCORM package to open Add SCORM package.
Upload the original SCORM ZIP and wait for validation and security processing. Do not upload an ordinary document ZIP or place the exported course inside an extra enclosing folder.
Insert the validated package. Keep a copy of the original course export outside Beetl so its author can correct packaging problems.
2. Set the Reader presentation
Select the SCORM activity and choose Activity settings from its editing toolbar.
Set the Activity title and optional Short description and cover. Choose Theater overlay or Inline in article, and decide whether to Allow fullscreen.
Expand Package information to check the detected version and package details. Choose Save settings when ready, then preview the article.
3. Test launch, resume, and completion
Publish the test article when its audience and content are correct. Open its Reader address as the intended signed-in learner and choose Start activity or Resume activity.
Work through the package, leave after it has saved progress, and reopen it with the same account. Check the bookmark, completion state, and score only where the package supplies them.
For a package with several learning activities, test the activity selector and the required paths. Test the actual course on the devices your learners use.
SCORM progress is saved separately. It does not count toward Guided Journey completion and is not included in Insights or learning reporting. Do not use the article editor preview as proof of an assigned learning result.
4. Update a course carefully
Select Replace SCORM package only when you intend to upload a revised course. Read the learner-registration warning before confirming replacement.
Check the new package and Reader presentation before republishing the article. Test resume and completion again; do not assume an incompatible replacement can reuse earlier course state.
Check your result
The intended learner can launch the published activity and resume supported progress, and you understand which records the package supplies.
If something goes wrong
Package rejected: check the 50 MB limit, ZIP format, root imsmanifest.xml, and referenced launch files. Ask the course author to export a valid SCORM package.
Activity will not open: confirm SCORM availability, article access, security processing, and the environment’s SCORM service with your Admin.
No score or completion: confirm the package reports that value and that the learner used the same signed-in account. A launched course is not evidence of completion.
Journey progress is unchanged: this is expected for SCORM. Use supported journey activities when tracked journey completion is required.