Publish once. Deliver through verified customer LMS paths.
Stop rebuilding the same course for six different systems. With SCORM Dispatch you publish a package once and route it through supported customer LMS paths — with seat caps, expiry dates, and a one-click kill switch. You keep the source files; completions flow back to one dashboard.
What's a “dispatch,” exactly?
A dispatch is a small SCORM file your customer uploads to their own LMS. Instead of the actual course, it contains a secure pointer back to Allure Connect. When a learner clicks play, your real course streams from us — so you can cap seats, set an expiry, or shut it off, all without ever handing over your source files. Your customer just sees a course that works; you keep the controls.
From one upload to a validated customer-LMS delivery path.
Publish your package
Upload a supported SCORM package. Connect checks the manifest and launch file before destination-specific validation.
Create a dispatch
Name the customer, set access controls, and export a SCORM dispatch shell for the target LMS. Test that LMS and version before rollout.
Completions flow back
Your customer uploads the shell to their LMS. Learner completions, scores, and timestamps are recorded in your Connect dashboard as sessions update.
Licensing controls on every dispatch.
Allowed-domain enforcement
A launch only works from the customer's approved domain. Paste the shell anywhere else and it refuses to run.
Seat caps & expiry
Cap registrations per dispatch and set an expiry date. Optional access password for an extra lock.
One-click revocation
Revoke a dispatch from Connect without touching the customer's LMS or chasing a takedown.
Activate a new version centrally
Choose the active package version centrally, then re-run the acceptance path for affected destinations before broad rollout.
Per-client reporting
See launches, completions, and pass rates broken out by customer and course — audit-grade evidence per dispatch.
Embeddable launch URLs
Prefer a link to a shell? Drop a launch URL into your own product, portal, or marketing page — same guardrails apply.
How the runtime actually stays in your hands.
The shell your customer uploads is a thin SCORM wrapper. At launch it opens a Connect-hosted player and we mint a short-lived, signed session token — the course content is streamed server-side and never lands in the customer’s LMS. Completion data is reconciled back through the SCORM API and mirrored into your xAPI Learning Record Store.
- SCORM 1.2 & 2004 dispatch shells with xAPI records
- Short-lived session tokens minted at launch, not embedded in the shell
- Allowed-domain referer checks reject off-domain launches
- Idempotent completion callbacks; Connect remains the system of record
POST /v1/dispatches { "package_id": "pkg_01HXFV9P", "destination": "Acme · Cornerstone", "allowed_domain": "acme.csod.com", "seat_cap": 1000, "expires_at": "2026-04-12" } ← 201 · shell ready { "id": "dsp_4KXQ", "status": "live", "shell_url": "…/dsp_4KXQ/scorm.zip" }
What sits on top of dispatch.
Validate one course across your target customer LMS paths.
Get a sandbox key and create your first dispatch — no credit card.