Program Management
What it does
Section titled “What it does”The Studio catalog is the backbone of every program in an Organization: all teaching content lives in a single hierarchy that runs Collections → Pathways → Courses → Sections → Lessons → Elements. Content authors build and maintain that hierarchy in Studio; Administration manages the Spaces that group the people who receive it and the Labels that categorize records across the platform. Content structure and people grouping are kept separate by design — a program is defined once in the catalog and delivered to any number of Spaces.
Key objects
Section titled “Key objects”Program management introduces the six catalog levels plus the two organizational objects that sit outside the catalog.
| Term | Definition |
|---|---|
| Collection | The top-level catalog container — a full subject or learning track. Created with a name, a public/private status, and a cover image. Studio also labels this level “Catalog”. |
| Pathway | A Collection presented to learners as an ordered sequence of Courses toward a broader goal. Campus treats Pathways as designed to be completed in order. |
| Course | A defined topic inside a Collection, divided into Sections. Authored in Studio as an Index. |
| Section | A logical grouping of Lessons within a Course — one teaching unit. |
| Lesson | The unit learners open in the Lesson Player; it holds the Elements. Authored in Studio as a Component (also labeled Topic). |
| Element | A single interactive item — question, activity, or media — inside a Lesson. |
| Space | A virtual classroom or group that organizes Students, Staff, subjects, and teams. People belong to Spaces; content does not. |
| Label | A color-coded tag applied to students, tasks, and Spaces for filtering and categorization. |
Configuration
Section titled “Configuration”The documented options at each level are:
| Object | Options |
|---|---|
| Collection | Name, status (public or private), cover image; duplicate (clones all Courses, Sections, and Lessons inside); delete |
| Course | Title, cover image; drag-reorder within the Collection; duplicate; delete |
| Section | Title; drag-reorder within the Course; delete |
| Lesson | Title; opens in the Quiz Builder for Element authoring |
| Space | Name and icon at creation; actions: Edit, Add Student, Add Label, Archive, Remove |
| Label | Name and color at creation; name, color, and description editable later; delete |
Element-level authoring and settings are covered in Assessments.
Studio access is role-based: Owner has full access to content, assignments, results, and settings; Admin covers content management, assignments, and analytics; Editor creates and edits content and quizzes; Teacher works with assignments, live sessions, and results rather than authoring.
Constraints and edge cases
Section titled “Constraints and edge cases”- Hierarchy depth is fixed at the documented levels. Each level nests only inside the level above it; no other nesting is documented.
- Content lives in the catalog; people live in Spaces. Enrollment never changes catalog structure, and editing the catalog never changes Space membership. Assignments are the documented link between the two — see Course delivery.
- Naming differs by surface. Studio’s authoring UI presents five levels and labels the top container Collection, Catalog, or Pathway interchangeably; its internal names are Index (Course), Section (also Lesson or Module), and Component (Topic) for the Lesson level. Campus distinguishes a standalone Course from a Pathway, which is a sequence of Courses in a set order.
- Deletion cascades. Deleting a Collection removes everything inside it; deleting a Course removes its Sections and Lessons; deleting a Section removes its Lessons.
- Duplicating a large Collection takes time to complete; the operation should finish before further navigation.
- Assignments reference catalog content at the Collection, Course, Section, or Lesson level.
- Space deletion is permanent, restricted to admins or space owners, and may impact linked tasks or workflows. Archiving a Space disables it without losing data.
- Labels are flat — a name, a color, and an optional description. They apply across students, tasks, and Spaces and are the documented mechanism for cross-cutting categorization. Deleting a Label is permanent.
- A Collection’s public/private status is its only documented visibility setting at the catalog level; learner access otherwise follows enrollment and assignments.
Works with
Section titled “Works with”- Course delivery — how catalog content reaches learners through publishing and assignments.
- Assessments — the Quiz Builder that authors Elements inside Lessons.
- Multi-tenant hierarchy — how Organizations and Spaces are structured and administered.
- Enrollment — how Students enter Spaces and gain access to programs.
- Portal docs for procedures: Studio Catalog, Collections & Pathways, Courses & Sections, Elements, Administration — Spaces, Administration — Labels.