Publish & share.

From /teacher/courses, select a course. The header card has a Publish button. Click it; a modal opens with two radio options and (conditionally) a checkbox.

Default. Only people in the cohort can join the course. Whitelisted-but-pending students still join automatically on first sign-in (the cohort flow handles them); everyone else gets a permission-denied page if they try to access the course URL.

Use enrollment mode for institutional courses where you control the roster. It’s the right answer for almost every classroom context.

The studio generates a 6-character invite code (mixed alphanumeric — example: QF7XBV). Share the code via whatever channel you want (Slack, email, posting it on a slide). Anyone with a Studio account who enters the code at /teacher joins the course.

Use open mode for workshops, public courses, or any context where you don’t want to maintain a roster manually. The code is rotatable — re-publish the course in open mode to get a new one if the old one leaks.

When mode is open, a checkbox appears: List in Learning Commons. Tick it to add the course to /commons — a shared course catalog visible to every teacher in Studio. Other teachers can browse, preview, and clone (but not modify) your course.

Use Commons listing when you want to publish a course as a teaching resource for other instructors. Don’t list anything that contains material you’re still iterating on; once cloned, the clones diverge and your edits won’t propagate.

You can list and unlist freely — just re-publish with the checkbox toggled. Existing clones aren’t affected by un-listing.

The course header pill flips from draft (yellow) to published (green). The cohort panel still works exactly as before — Send invites, Add student, Import CSV are all still active. Students who were pending now see the course in their dashboard the next time they sign in.

You can keep editing lessons after publishing. The studio doesn’t freeze a course on publish. Edits are visible to students who haven’t entered a session yet; in-flight sessions keep the old lesson context for that session’s lifetime.

There is no “unpublish” action. The two transitions out of published are:

• Archive — sets status = archived. Use at the end of a term. Lessons and roster become read-only; new students can’t join.
• Delete — permanently removes everything. Don’t use unless you really mean it.

If you published by accident and want to “unpublish,” the right move is Archive plus a follow-up Clone if you need the content for a future term.

You now have a published course with a roster ready to receive invitations. If you haven’t already, see 06 / Send invite emails to bulk-send sign-in invitations to every pending student.

If anything misbehaves, see 11 / Troubleshooting.