Welcome!

Concepts and glossary

TL;DR; Every term used across this documentation, defined once, in the order things contain each other.

Read this page before any other. Later pages assume you already know what a delivery run is, what a library is, and why some things have more than one name.

Why some things have two names

Lupo's code and Lupo's product don't always agree on what to call something — the code was written first, and some product-facing names changed later without renaming the underlying tables. This documentation always uses the product name. Where it matters, both are listed below.

Code says Product says
Cohort Delivery run
Instance Session, or "Day N of M"
Section Module
Channel / course type Delivery type
TinyUrl Course code

The knowledge base chain

Company → Department → Collection → Knowledge Base → Library → Folder → File

  • Company — the top-level tenant. Everything else belongs to exactly one company.
  • Department — a subdivision of a company. Departments are where courses and knowledge bases actually live.
  • Collection — the picker you land on after choosing Knowledge in the nav; it groups departments so you can get to a specific knowledge base.
  • Knowledge Base — one per department. The searchable, AI-readable corpus for that department.
  • Library — a folder-like grouping of content inside a knowledge base.
  • Folder — a subdivision inside a library. Folders can nest inside each other.
  • File (a "content item") — the actual document, video, or transcript. This is the unit Ask Lupo reads from and cites.

The course chain

Course family → Offering → Course → Module → Lesson → Activity

  • Course family — the identity that ties together the same course sold in different ways (for example, the same class offered as On-Demand and again as Self-Paced). A family has a name and an owner, but no page of its own — you never "visit" a family, only a specific course inside it.
  • Offering — what the code calls a "delivery type" or "channel": Full, On-Demand, Self-Paced, or Instructor-Led. Each offering is its own course record, sharing the family identity.
  • Course — a specific, enrollable offering. This is the level learners enroll in and where progress is tracked.
  • Module — an ordered group of activities inside a course (the code calls this a "Section" — always say Module here).
  • Lesson — an optional grouping of activities inside a module. Either every activity in a module has a lesson, or none do — there's no in-between.
  • Activity — the leaf-level thing a learner does: watch a video, read something, take a quiz, work through a Student Guide, and so on.

The delivery-run chain

Delivery run → Day → Registration → Attendance

This chain only applies to Instructor-Led courses.

  • Delivery run — one scheduled instance of an Instructor-Led course: its own roster, capacity, waitlist, and status. A one-day class is a run of one day; an eight-day class is a run of eight days.
  • Day — a single session inside a run, with its own date, timezone, and join link. Registration, capacity, and the waitlist all live on the run, not on the individual day.
  • Registration — a learner enrolling into the run as a whole, not into a specific day.
  • Attendance — recorded per day, per learner. A multi-day run tracks attendance separately for each day, because one learner can attend some days and miss others.

Where to go next