---
title: "What is the new course builder, and what does it mean for my integration?"
description: "What the course builder gives your users, how it differs from Classic, and what changes in your integration."
canonical_url: "https://support.coassemble.com/articles/what-is-the-new-course-builder-and-what-does-it-mean-for-my-integration-ROn3TQyCYQ"
md_url: "https://support.coassemble.com/articles/what-is-the-new-course-builder-and-what-does-it-mean-for-my-integration-ROn3TQyCYQ.md"
---
# What is the new course builder, and what does it mean for my integration?

> What the course builder gives your users, how it differs from Classic, and what changes in your integration.

The new course builder is a second authoring experience available through the same builder embeddable you already use, selected by setting `options.legacy` to `false`. Your users get an AI agent that builds a course with them, and screens made of blocks they arrange themselves, in place of the fixed screen types in Classic. It is in public beta, which means it is stable and ready for real work and will keep improving.

Nothing changes in your product until you ask for it. An integration that opens the builder without specifying which one to use gets Classic, exactly as it does today.

## What do my users get that Classic does not give them?

**A single creation flow.** Your user brings a document or describes what they want, answers a few questions, and watches a structured course get built. They choose how closely the course follows their source material: Verbatim keeps their wording as written, which suits policies and compliance content, Structured reorganises it into a learning flow, and Adaptive rewrites and expands it.

**Screens made of blocks.** In Classic, the screen type decides the shape and content has to fit it. In the course builder, your user places blocks on a six column grid and any block can sit on any screen, so one screen can hold an explanation, an interactive element and a knowledge check together. Every screen starts from a layout, so spacing and hierarchy stay consistent.

**An agent that stays in the builder.** Your users describe changes rather than hunting through menus. The agent can add screens, rework wording, adjust tone or reading level, insert knowledge checks, reorder screens and reshape the course.

**Courses grouped into sections.** Learners see them as chapters with their own progress, so a long compliance course reads as manageable pieces.

**Course Coach.** On-demand review of a finished course covering instructional quality, engagement and accessibility, with each finding linked to the screen it refers to. Course Coach is not included on every plan. If it is not included, your users will not see the Review and Insights tabs and everything else works normally.

## What changes in my integration?

One flag. `options.legacy` selects which builder loads: omit it or set it to `true` for Classic, set it to `false` for the course builder. The endpoint, signed URL issuance, `identifier`, `clientIdentifier`, `themeId` and the emitted events all stay as they are.

The course builder works only with courses built for it, and Classic works only with Classic courses. Issuance rejects a mismatch, so your product needs to know which type a course is before it opens the builder.

## Which of my users see it?

You decide, and you can decide per session. `legacy` is set each time you issue a builder session, so you can put a pilot group into the course builder while everyone else continues in Classic, or offer both and let your users choose.

The feature toggles are yours too. `ai`, `googleDrive`, `oneDrive` and `feedback` default to on. `publishing`, `narrations`, `translations` and `loom` default to off. What your users actually see is the combination you configure, so two partners can expose quite different experiences from the same builder.

## What stays the same for my existing content?

Courses your users have already built stay in Classic and keep working exactly as they do today. Their learners see the same experience, sharing is unchanged including links, embedding and SCORM export, and collections, folders, enrolments, reporting and history are all unaffected.

## Frequently asked questions

### Do I have to switch?

No. Classic is what loads when you do not specify a builder, so your integration continues unchanged until you decide otherwise.

### Can my users move an existing course into the course builder?

Not currently. A course lives in the builder it was made in, and a migration mechanism is being worked on. Duplicating a Classic course gives you another Classic course.

### Is public beta safe to put in front of my customers?

It is stable and ready for real work, and it will keep improving while your users are in it. Decide the rollout pace that suits your customers, since you control who sees it.

### What is the accessibility position for course builder courses?

The Classic learner experience is independently verified as conforming to WCAG 2.2 Level AA by Modality Co. The new course builder learner view is in public beta and has not yet been independently verified, however Coassemble's own accessibility testing shows it meets WCAG 2.2 Level AA.