What is SCORM?
SCORM (Sharable Content Object Reference Model) is an industry standard for e-learning content. SCORM packages are interactive learning modules created in authoring tools like Articulate, Adobe Captivate, or iSpring. Juno supports SCORM 1.2 and SCORM 2004 packages. It also supports xAPI / TinCan content, and your AI assistant can build a SCORM-tracked HTML lesson for you.Taking SCORM content
When you open a SCORM unit in Juno:1
Content loads in the viewer
The SCORM package opens in an embedded viewer within the Juno interface.
2
Work through the module
Navigate the content at your own pace. Your progress is tracked automatically by the SCORM package.
3
Completion recorded
When the module reports completion, Juno records it and updates your progress.
Completion tracking
SCORM packages control their own completion logic. Juno supports two evaluation methods:If you’ve finished the module but Juno still shows it as incomplete, the package may not have sent a completion signal. Contact your admin.
Common issues
SCORM analytics
In Admin → Analytics → Unit analytics, the learner breakdown table for SCORM units can include an Attempts column showing how many times a learner launched the package.The Attempts column is off by default. Contact your CSM to enable it for your organization.
Building a SCORM unit from HTML
You don’t need an authoring tool to make a SCORM unit. Your AI assistant, connected through the Juno MCP server, can build an interactive HTML lesson, preview it, and save it in Juno as a SCORM-tracked unit. It works in a draft workspace that learners can’t see, and the saved lesson is live immediately. You can edit it later, preview earlier versions, and restore one. See HTML Lessons for the full workflow, including version history. For xAPI packages, see xAPI Content. To bring in an existing SCORM ZIP, upload it in Juno — see Uploading SCORM content.Uploading SCORM content
1
Create a new SCORM unit
Click + Create, hover New, and choose SCORM.
2
Upload your ZIP file
Drop the SCORM package as a ZIP file onto Drag & Drop your SCORM Zip file to upload. Juno extracts and validates the package automatically. The package’s files must sit at the root of the ZIP, not inside a folder. Juno supports files up to 1 GB, and larger files may not upload well.
3
Configure settings
Set due dates, evaluation method (completion or score), standalone mode, audience, and tags (see below).
4
Add tags (optional)
Use the Tags field to categorize the unit. Start typing to filter existing tags, or type a brand-new tag name and press Enter to create it on the spot — see Tagging SCORM units below.
5
Publish
Publish to make it available in the Company Academy or add it to a Course/Journey.
Previewing and replacing a package
Open a SCORM unit’s editor to preview what you have or replace it.- Preview a version. Under Version history, select Preview on any row to play that version in a new tab. Preview changes nothing and does not affect what learners see. Preview works for packages you uploaded, such as Articulate Rise exports, as well as for lessons built with your assistant. See HTML Lessons for how versions and Restore work.
- Re-upload a package. In the same editor, drop a new ZIP onto Drag & Drop your SCORM Zip file to upload, then select Update. Juno validates the new package the same way it does on first upload. Because learners who already started the unit can be affected, Juno asks you to confirm before it uploads.
- Download the current package. Admins see a Download link above the upload area.
Finding SCORM content in search
SCORM units are searchable by what’s inside them, not only by their title. When a learner searches the Company Academy, Juno looks at the text it can read from the package — section titles, on-screen text, and caption files — alongside the unit title, tags, description, and creator. This means a learner can often find a SCORM unit by searching for a phrase from one of its screens, even when the unit’s title says nothing about it.What Juno can read
Juno reads what it can from each package, but not every package has text it can reach. Some authoring tools store their text in a format Juno can’t read, and some packages are published as video or animation with no readable text at all. Very long packages are indexed up to a size limit, so text near the end of a long course may not be searchable.
Narration is not searchable on its own. Juno reads text, not the words spoken aloud. If a lesson carries a lot of its meaning in voiceover, add a caption file (.vtt or .srt) and link it from the lesson’s main page — Juno reads caption files that ship inside the package, and that narration then becomes findable.
Juno never opens a package to a learner differently based on this. Content that can’t be read for search still plays exactly as normal — the only difference is how learners find it.
Check a unit’s search status
Open a SCORM unit’s editor and scroll to Search: “How learners can find this unit in the Company Academy.” It shows what Juno found inside the package.If your content isn’t turning up in search
1
Search for a phrase from inside the unit
Pick a distinctive sentence from one of the unit’s screens and search for it in the Company Academy. If the unit appears, its text is indexed.
2
Add a description
A short summary in the unit’s description is always searchable, whatever the package contains.
3
Add tags
Tags are searchable and filterable for every SCORM unit. For packages Juno can’t read inside, they’re the main way learners will find the content — see Tagging SCORM units below.
4
Consider rebuilding it in Juno
Content built in Juno keeps its text where search can read it, and stays searchable when you edit it. If a package is important and hard to find, rebuilding it in Juno gives the best result.
Tagging SCORM units
Tags help learners and admins find SCORM units in the catalog, filter analytics, and group related content. From the SCORM editor you can both reuse existing tags and create new ones without leaving the form.When to use it
- You’re uploading a new SCORM package and the tag you need doesn’t exist yet.
- You want to align SCORM content with the same tag taxonomy used across courses, learning paths, and analytics.
- You need to attach a missing tag without leaving the editor to open Admin → Tags.
How to add tags
1
Open the Tags field
In the SCORM editor, scroll to the Tags section and click into the field.
2
Select existing tags
Start typing to filter the company tag list. Select one or more tags — they appear as chips inside the field.
3
Create a new tag inline
If no match exists, finish typing the tag name and press Enter. Juno creates the tag as a company skill, saves it to your tag library, and attaches it to the unit in one step.
4
Save the unit
Save or publish the SCORM unit. New tags are immediately available to other admins from any tag picker.
Tag names must be unique. If you try to create a tag that already exists (even with different casing or as a hidden index entry), Juno shows a Tag already exists error and keeps your selection unchanged — select the existing tag from the dropdown instead.
Example
You’re uploading a compliance refresher for the EMEA region and want it grouped with other regional content:- In Tags, type
EMEA Compliance 2026. - The dropdown shows no match.
- Press Enter. Juno creates the EMEA Compliance 2026 tag and adds it as a chip on the unit.
- Publish the unit. The new tag is now selectable on other units, courses, and learning paths.