Plan Comparison

Basic and Pro plans support SCORM packages exported from Articulate Rise 360, Articulate Storyline 360, and Adobe Captivate. Support for alternate and custom SCORM authoring tools is available on the Enterprise tier.

SCORM License Manager supports two types of registration limits when configuring a license for your customer:

• Course Registration Limit: Each new course launched by a unique user during the term of the license will deduct one use from the registration limit. Modules belonging to the same course will not deduct an additional use.
• Learner Registration Limit (Pro/Enterprise Only): Each new unique learner will deduct one use from the registration limit the first time they launch a course from the Series linked to the license. The learner can subsequently access any number of courses from the series without deducting additional uses.

Course content is organized into three levels:

• Module: A module represents the actual SCORM package being distributed to customers. This could be a full course, or a portion of a course such as a section of videos or a standalone assessment. Completion and activity statistics are tracked at the module level.
• Course: A course is a collection of one or more modules used to track the number of redemptions against a license. Launches of multiple modules within the same course count as a single course registration.
• Series: A series is a collection of one or more courses and is used in the order fulfillment process. The content available to an organization is based on the Series selected during order fulfillment. Pro and Enterprise customers can configure licensing to allow learners to access multiple courses from the same series using a single redemption.

SCORM License Manager supports three flexible verification methods to work with your existing LMS environment:

• LMS Domain Verification: Whitelist your LMS domain for automatic authentication. When a learner launches a course, the package verifies the request is coming from an approved domain.
• Token-Based Authentication: Use a unique API token passed with each launch request for secure verification. Ideal for environments that require explicit authentication on each session.
• Embed Token: A verification token is embedded directly into the SCORM package for simplified integration. Best suited for organizations that need a streamlined setup with minimal LMS configuration.

All three methods are compatible with any SCORM-compliant LMS platform.