Skip to content

What happens to my existing courses if I am using the new course builder experience?

What changes for courses you have already built now that the new course builder is available.

Nothing changes. Every course you have already built stays exactly where it is, keeps working exactly as it does today, and is unaffected by the new builder. The new builder appears as an extra option when you create a course, alongside the Classic builder you use now.

What stays the same?

For courses you have already built:

  • They open in the Classic builder and you edit them the same way you always have. Their cards in the dashboard carry a Classic badge, so you can tell at a glance which is which.
  • Learners see the same experience they see today. The rebuilt learner view applies to courses built in the new builder, so nothing changes for people partway through one of your existing courses.
  • Sharing is unchanged. Existing links keep working, along with email invitations, Slack, embedding and SCORM export.
  • Collections, folders and enrolments carry on as they are.
  • Reporting and insights are unchanged, and your history is intact.
  • Classic itself is unchanged. Every screen type, feature and setting works as it did before.

Can I move an existing course into the new builder?

A course lives in the builder it was made in, so if you want a course in the new builder, you start it there.

Which builder do I get when I create a new course?

The new builder appears as an option alongside Classic each time you create a course, so you can try it on your next course while continuing to build everything else the way you do now. Nothing is switched over for you.

What about courses created through an integration?

If you have Coassemble embedded in your own product, nothing changes for your users by default. An integration that creates a course without specifying which builder to use gets the Classic builder, exactly as it does today. The new builder is opt in, so your application has to ask for it explicitly before your users see it.

Two things are new on the integration side, and both are additions rather than changes to what you already run:

  • Screen embeddables. You can now work with a single screen rather than a whole course. Screen Builder puts the new builder's screen editor inside your own application, and Screen Player renders one screen for a learner. A standalone quiz embeds as a set, with scoring, retakes and results.
  • SCORM hosting. You can upload an existing SCORM package and host it in Coassemble alongside authored courses, with attempt tracking and question-level results.

Your existing course-level embeddables keep working exactly as they do today.

Frequently asked questions

Will my learners notice anything?

No. A course built in Classic looks and behaves for learners exactly as it did before, including for anyone partway through it. Courses created in the new builder have an improved learner navigation experience.

Can I duplicate a course and convert the copy?

Duplicating gives you another Classic course, so a copy doesn't get you into the new builder. Duplicate when you want another Classic course to work from.

Will my usage allowances be affected?

Your allowances work the same way regardless of which builder you use. Anything that consumes narration tokens or image generation counts the same in both.