The Vidext data model

Everything in Vidext hangs off one hierarchy. Learn it once and the whole product — and the API — makes sense.

The containers

• Organization — your workspace and the boundary for everything: people, content, knowledge, billing, and settings. Data never crosses organizations.
• Team — a group of people inside the organization (a department, a region, a cohort). Teams are how you control who learns what.
• Course — a playlist that references and orders modules around a goal, such as "Sales onboarding." It points at live modules rather than owning them.
• Module — the unit people actually learn from: a narrated, interactive experience Vidext builds for you. Modules stand on their own, so the same one can appear in several courses. Creating one from the chat home adds it to your module library; you add it to a course when it's ready.
• Chapter — a section within a module, grouping the scenes a learner moves through.
• Document — a source file or imported page that grounds generation: the raw knowledge Vidext structures into learning.

How access flows

The link that grants learners access is assigning a course to a team:

1. You assign a course to one or more teams.
2. Every member of those teams is enrolled in the course's modules automatically.
3. When someone new joins the team, they are enrolled in already-assigned courses too.

So you never manage learner access module by module — membership and assignment do the work. See Enrollments.

Status lifecycle

Courses move through three statuses:

Modules don't carry a status of their own. A module is published when it has a live published version: each publish freezes an immutable version of the content, and learners always see the most recently published one. Archiving a module hides it without deleting its history.

Releasing a course, like publishing a module version, is always an explicit human decision. See Draft and published.