Welcome!
-
-
- Learn Home
- Core Concepts
- Companies and Departments
- Courses
- Course Status and Visibility
- Sections
- Video Activities
- Reading Activities
- Document Activities
- Enrolling People in a Course
- Bulk Enroll With CSV
- Roles in a Course
- How Progress Is Tracked
- Course Reports
- Knowledge Base Overview
- Libraries and Folders
- Uploading Content Items
- Library Visibility
- AI Agent per Library
- My Courses
- Platform People
-
- Project Structure Template
- Table of Contents (TOC)
- Content Folder
- Introduction to Markdown
- Markdown Basics
- Markdown Lists
- Markdown Links
- Markdown Images
- Markdown Code
- Markdown Tables
- Markdown Equations
- Markdown Videos
- Markdown Embedded HTML
- VS Code Snippets
- Introduction to Styles
- Framed Narrations
- Markdown Configuration
- Editor Setup
-
Waitlist and Capacity
TL;DR; Every delivery run has a capacity and a waitlist switch, and the waitlist is on by default. Once a run is full, new registrants land on the waitlist instead of being turned away; when a seat opens up, Lupo promotes the next person automatically and emails them.
Before you start
You need a scheduled run. See Schedule a class if you haven't created one yet.
Steps
Capacity and Enable waitlist when full are set on the run itself, not per day — you set them when creating the run (see Schedule a class, step 2). Leaving capacity blank means unlimited, so there's never a waitlist to form.
Once the run reaches capacity, the next person to register doesn't get turned away — they're placed on the waitlist, in the order they registered, and told "This session is full — you've been added to the waitlist and will be registered automatically if a spot opens." A roster import row lands the same way: "The session is full, so they were added to the waitlist."
When a seat frees up — someone registered cancels, you remove a registrant from the roster, or you raise (or clear) the run's capacity — the learner who's been waiting longest is promoted automatically. You don't have to do anything: they get an off-the-waitlist email, subject "You're in: " and headed "A spot opened up — you're registered for ", with the calendar file for all the class days attached; and if the run links a self-paced course, they get their seat on it under the run's Self-paced access opens rule — the same as a direct registrant.
If a promotion ever gets stuck — a crash, a stray registration — a background check re-sweeps every 15 minutes, and opening the run's page re-checks it too, so it clears on its own rather than staying stuck.
What this doesn't do
Capacity and the waitlist apply to the whole run, not to individual days — if a run has three days, they share one capacity and one waitlist; you can't cap one day differently from another. Lowering a run's capacity after people already have seats doesn't remove anyone who's already registered.
With Enable waitlist when full switched off there is no queue: a full run shows a disabled Full button, a learner who tries is told "This session is full.", and an import row reads "The session is full and has no waitlist."
Common issues
A learner says the session shows full. — Expected once the run hits capacity. With the waitlist on they see Join waitlist instead of Register and will be promoted in order if a seat opens; with it off, the button reads Full and nothing queues — raise the capacity or turn the waitlist on from Edit run.
Someone was promoted but says they didn't get an email. — Promotion and its "You're in" email usually happen together instantly. If it's been more than a few minutes, the background sweep should still catch it on its next 15-minute pass — check back shortly before treating it as broken.
Where to go next
- Enroll learners — the paths that put someone on a roster in the first place.
- Manage the roster — once people start registering.