> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/courses/scorm-courses/scorm-multi-lingual.md).
# Uploading SCORM with different Languages
Login to \https\://cloud.scorm.com/sc/guest/SignInForm\
Login to [**https://cloud.scorm.com/sc/guest/SignInForm**](https://cloud.scorm.com/sc/guest/SignInForm)
Select the **Organization (Realm)** you want to upload a **SCORM** course for.
Click on **Add Content** (Top Right Corner) and select **Import a SCORM, AICC, xAPI or cmi5 package**.
Specify a **Course ID** for the file you are uploading. Add the language code behind the Course ID you are adding, e.g. ***Planning-for-Your-Future-V1-en*** (for English) OR ***Planning-for-Your-Future-V1-fr*** (for French) OR ***Planning-for-Your-Future-V1-es*** (for Spanish).
Choose the **SCORM** or **xAPI** file you wish to upload by clicking on **Browse**. Once file has been selected, click **Import Course**.
Once the course has been uploaded, you are able to change the Launch behaviour in **Course Properties**. After your changes has been made, click **Save**.
The **Course ID** (e.g. Planning-for-Your-Future-V1) is what you use as the [**SCORM Course ID**](https://e02.insite.com/portals/portal/courses/scorm-courses/adding-scorm-courses)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.shiftiq.com/help/courses/scorm-courses/scorm-multi-lingual.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.