> ## Documentation Index
> Fetch the complete documentation index at: https://docs.exec.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Remix a Course

> Copy an existing course into a new draft and retarget it at a different audience with Course AI

Remixing takes a course you already have and makes an independent copy you can change freely. It is the fastest way to get a second version of good training: the same material framed for a different role, a different tenure level, or a different department, without rebuilding it and without disturbing the course your team is already enrolled in.

If you have remixed a roleplay scenario before, this is the same idea applied to a whole course. See [Remix a Scenario](/roleplays/remix-scenario) for the scenario version.

## When to Remix

Reach for a remix when the content is right but the framing is not:

* **A different audience.** A foundations course written for new hires, retargeted at tenured reps who need the refresher rather than the basics.
* **A different team.** The same framework taught to support, where the examples should be tickets rather than deals.
* **A different depth.** A long onboarding course cut down to a short version, or a short one expanded.
* **A safe place to experiment.** Try a restructure on a copy while the published course keeps running.

<Tip>
  If you only want to change the live course itself, you do not need a remix. Editing a published course already starts a new draft and leaves learners on the current version until you publish. See [Publish and Versioning](/courses/publish-and-versioning).
</Tip>

## Remix a Course

<Steps>
  <Step title="Find the course">
    Go to **Courses > Manage** and find the course in the list. Remix is available from the row's **...** menu, and from the actions menu on the course dashboard and in the builder header.

    <Frame>
      <img src="https://mintcdn.com/exec-79a6bbdb/TWRlEwyDDvKtFc1V/images/courses/remix-course-menu.png?fit=max&auto=format&n=TWRlEwyDDvKtFc1V&q=85&s=e43efdba12b07e9bb9e3c9eff531d096" alt="The course row actions menu open, showing Edit, Remix with AI, and Archive" width="3840" height="2160" data-path="images/courses/remix-course-menu.png" />
    </Frame>
  </Step>

  <Step title="Choose Remix with AI">
    Exec confirms what the copy will and will not carry over before it creates anything.

    <Frame>
      <img src="https://mintcdn.com/exec-79a6bbdb/TWRlEwyDDvKtFc1V/images/courses/remix-course-dialog.png?fit=max&auto=format&n=TWRlEwyDDvKtFc1V&q=85&s=e66c3e01d5e1bf1a8e57cc51571b4f37" alt="The Remix this course dialog explaining what the copy includes and excludes" width="1096" height="1004" data-path="images/courses/remix-course-dialog.png" />
    </Frame>
  </Step>

  <Step title="Select Start remixing">
    The copy is created as a draft named after the original with **(remix)** appended, and opens in the builder with the Course AI panel already open.
  </Step>

  <Step title="Tell Course AI what to change">
    Describe the new audience or framing and let it rework the copy. Because it is a full course, whole-course instructions work well here: retone it for a different level, translate it, shorten it, or split a section into several.
  </Step>

  <Step title="Rename and publish">
    Give the remix a real name in the course settings, then publish it as its own separate course. Until you publish, nobody sees it.
  </Step>
</Steps>

## What Carries Over

A remix is a structural copy, not a linked one. Once created, the two courses are independent: editing one never affects the other.

| Carried over                              | Not carried over                              |
| ----------------------------------------- | --------------------------------------------- |
| All sections, pages, and blocks           | Enrollments and learner progress              |
| Description, cover image, and theme color | Version history (the copy starts fresh)       |
| Course tags and group restrictions        | The linked certification                      |
| Self-enrollment setting                   | Published status (the copy starts as a Draft) |
| Email notification settings               |                                               |

Two details are worth knowing:

* **Roleplay scenarios and Knowledge Hub articles are shared, not duplicated.** The remix points at the same scenarios and articles as the original, so editing one of those scenarios changes it in both courses. If you want the remix to practice against something different, swap the block's scenario or generate a new one. See [Add a Roleplay](/courses/add-roleplay).
* **The copy starts from the published version.** If the original has never been published, the copy is taken from its current draft instead.

<Info>
  A remix is a new course, so it counts against your plan's course limit and needs a free slot to be created. Archived courses cannot be remixed. See [Plans and Feature Availability](/platform/plans).
</Info>

## Remix, Collection, or Restriction?

These solve different problems, and it is easy to reach for the wrong one:

* **Remix** when you need genuinely different content for a different audience. You end up with two courses that diverge.
* **A collection** when the content is the same and you only want it organized or easier to find. See [Collections](/courses/collections).
* **Group restrictions** when the content is the same and you only want to control who can enroll. See [Enroll Participants](/courses/enroll-participants).

## Next Steps

<CardGroup cols={2}>
  <Card title="Publish and Versioning" icon="rocket" href="/courses/publish-and-versioning">
    How the remix's draft, publishing, and version history work.
  </Card>

  <Card title="Collections" icon="folder-tree" href="/courses/collections">
    Keep the original and its remixes organized together.
  </Card>
</CardGroup>
