> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/library/scorm-packages.md).

# SCORM packages

Upload Sharable Content Object Reference Model (SCORM) packages to deliver compatible third-party learning content through Synap.

{% hint style="info" %}
**Location:** Library → Create or upload → SCORM file
{% endhint %}

### Upload a package

Upload the ZIP package as provided by the authoring tool. Synap reads its manifest and creates a Library item that can be previewed and delivered through a Course or Assignment. A valid ZIP file is not automatically a valid SCORM package: it must contain the expected manifest and launch files.

### What students experience

When a student opens the item, Synap launches the learning package and records the information the package reports. Depending on how it was authored, this can include completion, success status, score, time and the learner's saved position.

The package—not Synap—controls most of the lesson's internal navigation, wording and accessibility. Previewing the item therefore checks two systems working together: the Synap wrapper and the package itself.

### Display mode

| Mode           | Student experience                                     | Considerations                                                                                         |
| -------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------ |
| **Embedded**   | The package opens inside the Synap page.               | Keeps the student in context, but the available space is smaller and some packages do not resize well. |
| **New window** | The package opens in a separate browser window or tab. | Gives the package more space, but pop-up blocking and switching between windows can confuse students.  |

Choose the mode after testing the actual package. A desktop-focused course with complex menus may work better in a new window; a short responsive lesson may feel more natural embedded.

### Completion and scoring

SCORM packages decide what counts as complete and which score, if any, is sent back. Confirm whether completion requires opening, viewing every screen or passing an internal assessment; whether the package reports completion, success or both; whether it saves progress; and how the surrounding Course or Assignment treats that result.

{% hint style="warning" %}
If a package launches correctly but never completes, inspect its completion settings in the original authoring tool. Synap cannot infer progress that the package does not report.
{% endhint %}

### Before publishing

1. Confirm the package exports a SCORM version supported by your workflow.
2. Preview launch and navigation in the learner experience.
3. Complete a test attempt and verify completion or score reporting.
4. Check behaviour on the browsers and devices your learners use.
5. Close and reopen an unfinished attempt to check resume behaviour.
6. Complete every important outcome, such as pass and fail.

{% hint style="warning" %}
Do not unpack and recompress a package unless you understand its manifest structure. Small changes to the archive can prevent the content from launching.
{% endhint %}

### Replacing a package

Treat a replacement upload as a content release. Changes inside the package can alter navigation, completion and scores even when the Library item's title stays the same. Check current delivery, keep the source authoring file and version details, and retest the complete student journey before using the update with live learners.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://synap.ac/docs/platform/library/scorm-packages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.