Administrate is built around a small set of core objects. Understanding how these objects relate is essential, because most workflows—including importing data, scheduling, bookings, and reporting—operate on these relationships.
Course Templates
A Course Template defines what is being delivered. It contains reusable configuration such as:
- Default pricing.
- Duration and structure.
- Categories.
- Linked items and resources.
A Course Template does not represent a real-world delivery. It is a blueprint.
Events
An Event represents a specific delivery of a Course Template.
Events inherit configuration from the Course Template and then become the unit on which:
- Learners are registered.
- Instructors are assigned.
- Sessions are scheduled.
- Pricing becomes selectable.
An Event must exist before registrations (bookings) can occur.
Sessions
A Session represents a scheduled classroom occurrence within an Event.
- Classroom and blended Events have one or more Sessions.
- LMS-only Events do not have Sessions.
Sessions are where:
- Dates and times are defined.
- Instructors and locations are scheduled.
- Availability and conflicts are evaluated.
Learners
A Learner is a Contact participating in an Event.
- A single Contact may appear as a Learner in many Events.
- Each learner–Event relationship is independent.
Learners are associated to Events, not to Course Templates.
Relationship summary
- Course Templates define structure.
- Events represent delivery.
- Sessions represent scheduled classroom time.
- Learners represent participation.
Most system behavior flows from these relationships.