Shared courses | Your files

Publish a Compose course at its own link — no LMS, no account for the learner — and see who completed it.

Export a course from Compose, upload the package to Cloud, and press Share as course. You get a web address anybody can open. No LMS, no account for the learner, nothing to install.

To assign a course to your own people instead, with a deadline and a report, see Learn.

Part of Max (15 courses live at once) and Enterprise (unlimited, and restrictable to named people).

Publishing

Export from Compose as HTML5 or SCORM. Either produces a .zip.
Upload that .zip to Cloud like any other file.
Go to Shared courses and press Share as course.
Pick the package, give it a title, and publish.

Your browser decrypts the package, unpacks it and uploads the pages. The course appears at courses.mauvely.com/c/<name>/.

Where courses are served from

Courses are served from courses.mauvely.com, never from cloud.mauvely.com.

That is deliberate, and it is a security boundary rather than a tidiness one. A Compose course can contain custom code blocks — real JavaScript, written by whoever built the course. If that ran on the same origin as your vault, it could read your keys out of a tab you had unlocked. Serving courses from a separate origin is what stops it.

The practical consequence: a course cannot see your Cloud session, and your Cloud session cannot see a course. They are two different websites that happen to be run by the same people.

Who can open a course

Set this per course.

Anyone with the link

No name, no email. Progress is remembered per browser.

Ask for a name

A name and email before the course opens, so your report says who did what.

Named people only

Only addresses on your list. Enterprise.

Progress and completion

The course runtime saves progress as the learner goes, and reports completion and a first-try score back to you.

Progress is saved per learner. For an open course that means per browser — the same person on a phone and a laptop is two learners, and the report says so rather than pretending otherwise.
The report is yours. Completions, how far everyone else got, average score and average time, on the course’s own page in Cloud.
Mauvely does not aggregate it. There is no cross-course join and no global report. Someone taking two of your courses is two separate records, on purpose.

Taking a course down

Unpublish stops serving it immediately and frees one of your live-course slots. Learner progress is kept, so republishing next term picks up where it left off. Delete removes the files and the progress with them.