Welcome to this quick guide to trying out scorm-NEXT!

Next, we will take a tour of the tool to upload content, create a connector (SCORM dispatcher), register a client, and grant licenses. Finally, we will launch the content remotely from an external LMS.


The first step is to upload your contents to the scorm-NEXT repository. To do this, access the “Content repository” section of the main menu.

The contents can be organized into folders and subfolders to facilitate the management of large repositories.

Therefore, the first thing we will do is create a folder. Click the “New” button and write a name for the new folder.

Once the folder is created, we can upload contents to it. Click the “Import content” button and then press the “Choose file” button.

We can upload SCORM 1.2, SCORM 2004, and x-API packages, as well as videos in MP4 format and PDF documents.

Once the file is selected, click “Upload file” and wait…

At this point, we can continue uploading more content or continue with the next step, which will be to create the remote dispatchers for these contents.


In the “Connectors” section, we can create the remote dispatch packages of our contents to distribute them to multiple external LMS.

Like the repository, the connector catalog can be organized into folders and subfolders for easy management.

We will create a new folder to store our new dispatch package there. Click the “New” button, enter a name in the text box, and press the “Save” button.

Now press the “New connector” button. In the dialog that appears, we must choose in which format we want to create the dispatch package. Here we must select the same format as our contents. For example, if we have uploaded SCORM 1.2 content and we want to include it in a dispatcher, we must choose to create an SCORM 1.2 connector.

Once the format has been chosen, we must fill in the internal code or reference for this dispatch package, the title of the product, and optionally its description. We can also specify the number of training hours and the price of this product. This information will then be used in the Customer Portal.

By pressing the “Save” button, we will automatically access the Control Panel of this dispatch package that we have just created.

In this section, we must define the contents that will be part of this SCORM dispatcher.

Click the “Add contents” button. In the dialog box that appears, we can see the category tree of our content repository. We select the folder we created in the previous step.

In the right panel, we select, for example, the MP4 video and in the lower right we select the video element.

Finally, press the “Add” button, and we will see our first content in the dispatcher.

We press the “Add content” button again, and in this case, we select the SCORM content and the particular element (SCO) of that SCORM content.

Now that we have configured the content of our dispatch package (connector), press the “Exit edit mode” button to finish editing it.


To grant access to external LMS to our content, we must register those LMS in the “Clients” section.

Click the “New client” button. In the form that appears, we need to provide the reference or internal code of the client, their name, and optionally, a description.

Next, we must decide whether to use generic connectors or connectors specific to this client (remember: connector = dispatch package). Generic connectors are based on the URL of the client’s LMS and are the easiest option as they can be shared with multiple clients.

If we know the URL where the client’s LMS is located, we should select the “Use generic connectors” option and enter the most generic part of the URL in the “Origin” field, for example, “”.

If it’s not possible to know the URL of the remote LMS or the URL can’t be used to distinguish it from other clients (for example, Corner-stone), we must choose the “Use linked connectors” option. In this case, we don’t need to fill in any URLs for this client.

Finally, in the “Geographical Zone” dropdown, we can select the area in which our client is located to serve the content from the nearest location.

Click the “Save” button and access the control panel of this client to proceed with the next step.


In this section, we can manage how many available licenses that customer has on each of our connectors/dispatch packages.

Since we have not yet assigned licenses to this client, a wizard will ask us if we want to assign licenses now. Press the “Yes” button to continue.

In the dialog box that appears, we can see our folder structure in the “Connectors” section, where we have all our dispatch packages organized.

We select the folder and locate the product we created in a previous step. We mark the product and we enter the number of licenses we want to grant to this customer in the selected product or products. We must also specify the duration of the licenses and, optionally, we can specify a deadline from which no user will be able to access the selected product or products.

By pressing the “Add” button, we can verify that this client already has access to the connector (dispatch package) we created earlier and that it has the specified number of licenses.


We need to return to the “Connectors” section to download the dispatch package that we are going to test on an external LMS.

Locate the dispatcher we created and click on the “Download connector” button.

In this panel, we must first publish the dispatch package if it was not already published so that remote clients can access it. To do this, click on the “Publish now” button.

Once published, click on the “Download connector” button.

In the panel that appears, we can download the generic connector (dispatch package) in several formats (multi SCO, separate files, or with data anonymization).

In our case, since we chose the option to use linked connectors when we created this client, we will click on the button “I want to download a specific connector for a client”.

On the next screen, we will select for which client we want to download this dispatch package and click the “Select client and continue” button.

Now, in the dialog that appears, we will download the linked connector in the multi SCO format.


The next step is to upload this dispatch package to a SCORM-compliant LMS, such as Moodle.

To do this, it is essential to use a different browser (or an incognito tab) than the one being used with scorm-NEXT; otherwise, we will lose the session in scorm-NEXT when accessing the content from the remote LMS.

Once we have accessed the LMS as administrators, we create or update a course and upload our newly downloaded SCORM dispatch package to it.

Next, we go to the course and access the first element of the dispatch package that we have just uploaded.

We can see how the content is displayed directly from the LMS in a completely transparent way for the user.

Now we return to the browser where we are working with scorm-NEXT and press the “Reload” button located at the bottom right of the screen to update the list.

Here, we can observe how a license has been consumed, and the number of available licenses has been reduced in the same way.

Discover our scorm-cloud solution

Take a quick tour of scormNEXT. In this video you will discover how:

> To upload your SCORM content to the cloud

> To create your SCORM dispatch packages (connectors): courses, training pills, etc

>To register the LMS of your remote clients

> To send SCORM dispatch packages and set up licences for each client

> To view SCORM content remotely in an external LMS