NEW TO THIS? START HERE
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.
- Content providers selling to many clients
- L&D teams training partners & franchises
- Training resellers & course marketplaces
How it works
From one upload to a validated customer-LMS delivery path.
- STEP 01
Publish your package
Upload a supported SCORM package. Connect checks the manifest and launch file before destination-specific validation.
- STEP 02
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.
- STEP 03
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.
What you control
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.
FOR THE TECHNICAL BUYER
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_domains": ["acme.csod.com"],
"registration_limit": 1000,
"expires_in_hours": 2160
}
← 201 · dispatch created
{
"dispatch": { "id": "dsp_4KXQ", "status": "active", … },
"dispatch_url": "…/player/dispatch/…",
"expires_at": "2026-04-12T…"
}- Central package, isolated dispatches
- 1 → many
- Central package, isolated dispatches
- Time-bounded access controls
- Expiry
- Time-bounded access controls
- Webhook retry visibility
- Replay
- Webhook retry visibility
- Evidence export verification
- Signed
- Evidence export verification
Status, limits and plans
- Status
- Available
- Plans
- Every plan includes hosted SCORM runtime and dispatch. Free sandbox output is watermarked; paid plans remove the watermark. See plans
- Limits
- Packages: 3 (Free) · 25 (Starter) · 100 (Growth) · unlimited under fair use (Scale, Enterprise)
- Per dispatch: registration limit (seat cap), allowed domains, optional password, expiry
- Verify each target LMS and version before rollout
- Docs
- SCORM dispatch overview
Questions about SCORM Dispatch
What is SCORM dispatch?
How do seat caps and expiry work?
Which LMSs work with a dispatch?
How do completions come back?
session.completed can notify your own systems.PAIRS WITH
Works with
- Available
xAPI 2.0 LRS
Every completion lands in the integrated Learning Record Store; its June 6 local build passed 1,435/1,435 ADL suite checks.
- Available
Analytics & completion
Recorded completion and pass rates per customer and course, with anomaly detection.
- Available
Content Controller comparison
Compare controlled client-LMS distribution, standards, licensing, reporting, and operating models.
