Login Shopping Cart

Courses and content authoring

On this page

This article covers authoring courses on your training site: building the curriculum, uploading and updating SCORM packages, managing files in the Media Library, releasing content on a schedule, and controlling course visibility. It is written for platform admins working in the admin panel.

Where to find it

Sign in to your admin panel at /admin. In the sidebar you will use:

  • Courses > All Courses, the course list. Open a course to enter the course builder.
  • Courses > Categories, for organizing the catalog.
  • Courses > Listing Approvals, where organization-authored courses submitted for wider listing are reviewed.
  • Media Library, the file manager for every uploaded file, including SCORM packages.

Building a course

  1. Go to Courses > All Courses and create a course, or open an existing one.
  2. When creating, choose a Visibility setting: "Public (visible in course catalog)" or restricted (enrollment only).
  3. In the builder, the curriculum is organized as sections, which contain lessons, which can contain topics. Use each section's menu to Add Lesson, and each lesson's menu to Add Topic.
  4. Each lesson or topic has a content type: Text, Video, Loom, SCORM, Assignment, File, Slides, or Zoom Recording.
  5. The same page holds the course settings: Enrollment & Completion (self-enrollment, passing score, max attempts, enrollment expiry, certificate options), Release Schedule (Drip), the Mark Complete button behavior, SEO & Social, and the landing page content shown on the storefront.

Uploading SCORM packages

  1. In a lesson or topic, set the content type to SCORM.
  2. Upload the zip file exported from your authoring tool, or reuse a package already in the Media Library.
  3. The package is unpacked in the background. A "build" is recorded once extraction finishes, so a very large package may take a moment before it is playable.

All SCORM packages also appear in the Media Library under the SCORM packages filter, where each one has a details panel showing its builds.

Updating SCORM content safely

Replacing a SCORM package publishes a new build rather than overwriting the old one. Learners are pinned to the build they started, so an update never pulls content out from under someone mid-course.

  1. Open Media Library, select the SCORM package, and click Replace.
  2. A dialog titled "Publish a new build of this package?" asks what should happen to learners already part-way through, and shows how many there are:
    • Leave learners where they are (recommended). They finish on the build they started; new learners get the new one.
    • Move everyone across, keeping their place. Only for edits to existing slides, with nothing added, removed, or reordered. The platform verifies the upload is the same published package; if it is not, it falls back to leaving learners where they are.
    • Move everyone onto the new build. In-progress learners restart from the beginning. Completion, score, and time are kept.
  3. Click Publish build.

The package's details panel lists every build under "Package builds", with how many learners are on each. From there you can "Move learners here" (with an optional "Keep their saved place" checkbox) and "Retire" an old build to delete its files, which is only allowed once no learner is pinned to it.

The media library and file manager

Media Library is a full file manager: search, a grid or table view, and filters by file type (Images, SCORM packages, Videos, Audio, and more). Platform admins can also filter by organization; files are isolated per site, and each organization sees only its own.

Selecting a file opens a details panel where you can edit its title, alt text, caption, and description, copy the file URL, Replace the file in place (the URL does not change), or Delete it. Deleting warns you if the file is in use. The same picker appears anywhere you choose an image or file elsewhere in the admin panel.

Drip content and prerequisites

The "Release Schedule (Drip)" card in the course settings controls when learners can open each item:

  1. Set a rule on the whole course, a section, a lesson, or a topic.
  2. Rule types: unlock a number of days after the learner enrolls, unlock on a fixed date, or unlock after completing a specific lesson or topic.
  3. Optionally tick "Unlock lessons sequentially (each opens once the previous required one is completed)".
  4. Optionally tick "Email learners when a scheduled lesson unlocks".

When several rules apply to one item, the most restrictive wins. Free-preview items and anything the learner has already completed are never locked.

Separately, a course can require other courses as prerequisites. These are checked when the learner enrolls, and "Allow self-enrollment (including auto-enrollment after prerequisite completion)" can enroll learners automatically once they qualify.

Course visibility across organizations

  • Public (visible in course catalog) makes the course broadly visible on your storefront catalog.
  • Restricted (enrollment only) keeps it out of the catalog; learners reach it only through an enrollment, seat, or assignment.
  • On All Courses you can select several courses and use the bulk actions "Make Public" and "Make Private (Restricted)".
  • Courses never cross to other training sites; visibility only controls exposure within your own site and its organizations.

Why did this happen?

I replaced a SCORM package, but some learners still see the old content.

That is the default and it is deliberate. Learners are pinned to the build they started so an update cannot break their progress or their saved place. New launches get the new build. To move existing learners, open the package in Media Library and use "Move learners here" on the build you want.

I chose "Move everyone across, keeping their place", but learners stayed on the old build.

The platform double-checks that the new upload is the same published package as the current build. If the authoring tool's package identity differs, carrying saved places over would strand learners on bookmarks that no longer fit, so it quietly leaves everyone on the build they started instead.

Why can't I retire an old build?

Retiring deletes the build's files, and that is refused while any learner is still pinned to it, because those files are what they are reading. Move the remaining learners to another build first. Some builds also show that retiring frees no disk, because their files are shared with another build.

A learner restarted from the beginning after an update. Did they lose everything?

No. Moving learners to a new build without keeping their place clears only their saved position. Completion status, score, and time spent are always kept.

A lesson shows as locked for a learner, but I can open it fine.

Course managers bypass release rules entirely. The learner is seeing a drip rule: a day-delay from their enrollment date, a fixed unlock date, a prerequisite lesson or topic, or sequential unlocking. When several apply, the learner is held by the most restrictive one.

I set a course to Restricted, but enrolled learners can still open it.

Restricted means "enrollment only": it removes the course from the catalog and self-serve discovery. Anyone already enrolled, or given access through a seat or assignment, keeps their access.

Still stuck? Contact your support team through support.

Didn't answer your question? Contact support or browse the other Knowledge Base sections.