Welcome!

Core Concepts

TL;DR; The LMS has five building blocks: Companies, Departments, Courses, Sections, and Activities. A course belongs to a department, a department belongs to a company, and a course is a sequence of sections that each contain activities. Everything else in the LMS is a feature layered on top of those five.

If you're used to other LMS platforms, most of this will feel familiar. But there are a couple of Lupo-specific wrinkles worth knowing up front.

The container hierarchy

The LMS is structured as a tree:

Company
  └── Department
        ├── Courses
        │     └── Sections
        │           └── Activities
        └── Libraries (Knowledge Base)
              └── Content Items

Let's walk through each level.

Company

A Company is the top-level container. It represents an organization using Lupo — your company, or (if you're a consultant or a managed-services shop) one of your clients.

A single Lupo tenant can have multiple companies. That's useful when you're producing training for clients or when your organization has separate legal entities that need to stay isolated.

Everything below the company level is scoped to that company. Learners in Company A can't see Company B's courses. People with admin access to multiple companies can switch between them.

Department

A Department is a subdivision inside a company — "HR," "Engineering," "Sales Enablement," "Compliance." A company must have at least one department, but most have several. Departments are where courses actually live.

Departments also own libraries, which is where the Knowledge Base content goes. More on that in the Knowledge Base section.

Course

A Course is a self-contained learning experience. Learners enroll in courses, and they track progress at the course level. A course has:

  • A title and description.
  • A cover image.
  • A sequence of sections.
  • A list of people enrolled in it, each with a specific role.
  • A status (Draft, Published, or Archived) — see Course Status and Visibility.

Courses live inside a department. A course doesn't exist outside of a company/department — there's no "shared course across companies" in Lupo today.

Section

A Section is an ordered group of activities inside a course. Most courses have 3–8 sections, each containing 3–10 activities. Think of sections as the chapters of a textbook — they give the course structure and let you break a longer course into digestible chunks.

Sections have a title and an order. Learners usually work through them top-to-bottom.

Activity

An Activity is a single thing a learner does. Lupo supports several activity types, but only a few are fully implemented today:

  • Video — a player, optionally with Ask-My-Deck, an AI chatbot that answers questions about the video's content. This is the primary activity type in most Lupo courses.
  • Reading — formatted inline content the learner reads directly.
  • Document — a file (.md, .pdf, .txt) rendered inline.

Other activity types — Quiz, Assignment, Discussion, Code Exercise, External Link, Survey — exist in the data model but are not yet fully built out in the UI. Use Video, Reading, and Document today; the rest will come online in future releases.

See Video Activities, Reading Activities, and Document Activities for the details.

People and roles

Separate from the content hierarchy is the people side. Each person in the LMS has:

  • An account with an email and a password.
  • Memberships in one or more companies.
  • A role in each course they're enrolled in.

Each course has three possible roles: Student (takes the course, progress tracked), Observer (read-only access, progress not tracked), and Instructor (manages the course). A person can be a Student in one course and an Instructor in another — roles are per-course. See Roles in a Course for the full breakdown.

Libraries and the Knowledge Base

In parallel with courses, each department has one or more Libraries, which together form the department's Knowledge Base. A library is a folder of reference content — documents, videos, guides — that learners can browse or search, and that an AI agent can use to answer questions.

Libraries aren't courses and learners don't "complete" them. They're a reference layer. See Knowledge Base Overview for more.

Where to go next