Training has two connected branches. Courses and lessons teach; milestones, tasks and deliverables state what progress looks like. A path orders milestones for an enrollment. A cohort and groups can organize delivery, but neither is required to write lessons or enroll a person.
| If you are building… | Begin here | Then check |
|---|---|---|
| A self-paced program | Create a program, then courses and sections and lessons | Milestones and paths and tasks for evidence of progress |
| A coached intake | Follow the same content and proof steps | Cohorts and groups to organize a promotion and its members |
| An existing program with weak completion signals | Keep the content; start at milestones and paths | Add a task and expected deliverable |
These guides address an organization owner or admin who authors training. An organization-scoped program_director can read content and operate permitted delivery structures, but cannot create programs, courses or lessons. The cohort and group guide separates those duties.
Mike Academy wants an Agentic AI Developer program. Its Build an agent course contains a Tool calling section and a First tool call lesson. The Ship a working agent milestone receives a contribution from that lesson. A required Submit your agent demo task asks for a link to a working demo and a reviewer. Mike may deliver this program continuously, or add an October Builders cohort and a smaller Peer Lab group. These names illustrate the procedure; they are not preloaded customer records.
That example has two branches you can prepare independently:
Only a coached intake needs October Builders and Peer Lab. A self-paced enrollment can proceed without them.
The member journey explains how an enrollment turns this setup into unlocking, deadlines, submissions and reviews. For integrations, begin at the API reference; each guide links the authoring endpoints relevant to its step.