> ## Documentation Index
> Fetch the complete documentation index at: https://www.help.creatora.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Core concepts

> The Platform, Course, Student, Offer, Order, and access relationships used in API workflows.

These relationships help you combine GraphQL operations. The generated Types section of this API Reference shows the selected supported types, fields and arguments.

## Platform and Student

A **Platform** is the professional's branded space. Its Courses, Students, Offers and Orders belong to that Platform. Authenticated API requests use the current account and its Platform as context.

**Student** is the API's account entity. An account can have the `student` or `administrator` role. An Administrator is still represented by a Student record; there is no separate Administrator account type.

## Course, Module, Content and Level

A **Course** contains ordered **Modules**; each Module contains ordered **Content**. The current customer-facing content types are video lessons and quizzes.

A Course may also have **Course Levels**. A Module with no Level association belongs to the common curriculum for Course owners. A Level can unlock selected Modules for a Student who also has access to the parent Course. A Student can own more than one Level, and the accessible curriculum is the union of common Modules and Modules unlocked by those Levels.

```text theme={null}
Course
├── Modules ── Content
└── Course Levels ── access to selected Modules
```

Level-to-Module associations are live: changing them can change access for existing Students. A Level is not a second Course.

## Offer, Order and access

An **Offer** describes what someone can obtain. Every Course has an automatic base Offer. A custom Offer can include Courses, optional Levels for those Courses, Services and custom items.

An **Order** records a commercial attempt or a sale registered in Creatora. A successful Order can produce an **acquisition**, which records what was obtained, and Course or Level grants, which determine current learning access. A direct free Offer claim can create an acquisition without an Order. An Administrator can also grant Course access directly without creating an Order.

Decide whether an integration needs to **record a sale** or **grant access directly**. Those actions leave different commercial history. A Course Level grant requires access to its parent Course; removing the final Course-access source removes dependent Level grants.

Recipes show where each required `courseId`, `studentId`, `moduleId` and other ID comes from.