Coursor AI documentation
Coursor AI produces finished video courses, and a course can start two ways. Upload the handbooks, decks and manuals your organisation already owns and the course is built from that document. Or name a subject, get it mapped into one-hour skills, and produce those — with no document at all. Either way the platform writes, narrates and renders the lessons, and your team reviews and approves every course before it ships.
These pages are written for the people who will actually use it — whoever uploads the material, whoever reviews the scripts, and whoever presses approve.
Start here
Section titled “Start here”- Getting started — from an empty workspace to a first course, in order.
- Uploading source material — what is accepted, what is refused, and what the rights confirmation is for.
- Reviewing a course — the three points a course stops for a person: the plan before anything is written, the course document before anything is rendered, and the finished lessons before delivery. What to look at in each, and what you can change at each.
- Automated quality checks — the five layers, what they catch, and what happens when one fails.
- The delivery kit — every file in the download and what to do with it.
- Producing in another language — what changes, and what does not.
The shape of it
Section titled “The shape of it”Every course moves through six stages in the same order, and the platform enforces that order rather than trusting anyone to follow it:
| Stage | Who does it | What happens |
|---|---|---|
| Material | You | Upload files, confirm your rights to use them |
| Outline | Platform, then you | A syllabus from learning outcomes, evidenced from your material — then you read it, edit it and approve it, and nothing else is generated until you do |
| Review | You | Read and edit the outline, scripts, workbook and quiz. Confirm. |
| Produce | Platform | Narration, slides, assembly, and the presenter only where an avatar is set |
| Approve | Platform, then you | Five automated layers, then a human signs off |
| Deliver | You | Download the kit and publish it wherever you publish |
So a course stops for a person three times, not twice: nothing is written until the outline is approved, nothing is rendered until the course document is confirmed, and nothing is delivered until the finished lessons are approved. Budget three review sittings per course, not two. Those are states in the system, not conventions.
What this platform is not
Section titled “What this platform is not”It does not host a player for your learners and it never sees a completion — a SCORM or xAPI package reports to your LMS, which is the only system that stores it. There is no integration either: you download the package and upload it to the system you already run. If that is a problem, it is better to know now — the main site sets out what the product does not do alongside what it does.
When you have read enough
Section titled “When you have read enough”There are two ways in. You can send us one of your own documents, or name a subject and send nothing at all, and we produce the lessons and show you the review screen these pages describe, so what you are judging is a course of your own rather than a demo. Or you can open a workspace yourself: it starts on a trial, which writes your whole course and renders its first lesson.
Request a demo · Start a trial · Already have an account? Sign in to the console.