Course management
OrgHub administration for every institution course — browse the catalog, create and edit offerings, configure settings and capacity, enroll users, link modules, duplicate templates, and archive retired courses.
Course management in OrgHub is the institution-wide control center for every Fuxam course. While teachers and students work inside the LMS course shell for content, attendance, and grades, administrators use OrgHub → Management → Courses to see the full catalog, create new offerings, adjust identity and status, copy proven templates, retire old terms, and connect courses to the academic structure. This is FuxamCMS administration — not the day-to-day teaching workspace.
From the Courses page you can manage course details, add users at scale, configure how each offering behaves, and link courses to your academic database. The pages in this section walk through each part of that lifecycle, from first creation through enrollment, delivery support, and archival.
Why it matters
Universities run dozens or hundreds of course offerings each term — core modules, electives, continuing-education formats, and sandbox copies for faculty development. Without a single administrative view, course data fragments across departments: codes disagree, enrollments are hard to audit, and retired offerings clutter active lists.
OrgHub Courses gives authorized staff one authoritative table for the entire institution. That visibility supports accreditation review, term rollover, capacity planning, and alignment between what the curriculum promises (modules and cohort study plans) and what is actually delivered (linked LMS courses). Archiving instead of deleting preserves grades and history when a term ends but records must remain.
How this fits into Fuxam
Course management sits between academic planning and the LMS experience. Modules and curricula define the academic blueprint; study programs and cohorts assign that blueprint to student groups; OrgHub courses are the delivery containers teachers fill with learning journeys and sessions.
| Related area | Relationship |
|---|---|
| LMS Courses | The teaching and learning workspace inside each course — journey, calendar, grades, chat |
| Modules | Reusable academic units; courses can be linked to a module version for study progress tracking |
| Study programs and cohorts | Degree structures and student groups whose planned modules often map to course offerings |
| Module planning | Term-level planning that connects cohort curricula to organizers and delivery |
| User Management | Institution users who become course participants after enrollment |
| Institution settings | Institution-wide booking, waitlists, roles, and product switches that shape enrollment |
Key concepts
| Term | Meaning |
|---|---|
| OrgHub course | An institution course record with identity, settings, enrollments, and an LMS workspace |
| Course code | Institution identifier for the offering — auto-generated on create, editable inline in the Courses table |
| Course layer | Structural placement in your institution hierarchy; created automatically with each new course |
| Active vs Archived | Active courses appear in default lists; Archived courses are hidden from default views but data is preserved |
| Course Settings | Per-offering controls for capacity, LMS tabs, journey source, ratings, and connected modules |
| Capacity | Maximum participants for one course (unset means no limit) |
| Module-linked course | A course connected to a module version so academic tracking can align with the Database catalog |
| Learning journey database course | A course type tied to database-linked content — created through the link workflow, not the standard create sheet |
| Duplicate | An independent copy of content and settings without enrollments or module links |
Settings that affect courses
| Level | Examples | Where documented |
|---|---|---|
| Institution | Who may book courses, default booking role, waitlists; roles that unlock course management | Institution settings overview |
| Course | Capacity, Learning Journey / Chat / Drive / Calendar, SCORM vs Fuxam journey, rating schema, connected modules | Course settings |
| Access | Permission to create, update, or delete courses; permission to view or update course users and settings | Permissions, features and visibility |
Course lifecycle at a glance
Typical order: create or duplicate a course → edit identity and configure settings → enroll users or bulk-enroll → optionally link to a module → teachers deliver in the LMS → archive when the offering retires.
In this section
Browse and manage courses
Search, filter, and take actions on institution-wide courses from the Courses table.
Create a course
Add a new course and its starting structure from the Create sheet.
Edit a course
Update a course’s details, code, tags, and capacity from OrgHub or Course Settings.
Duplicate a course
Copy a course’s content and settings into a new independent offering.
Archive a course
Archive or restore a course, or delete it permanently when appropriate.
Manage enrollments
View, add, and remove individual course enrollments.
Bulk-enroll users
Add multiple users to a course at once using the bulk enrollment flow.
Course settings
Configure visibility, enrollment, grading, and course features.
Link courses to a database
Connect courses to module versions in your learning journey database.
Roles and responsibilities
| Who | Typical responsibility |
|---|---|
| Institution administrator | Full catalog oversight — create courses, edit codes, archive, delete (requires permission to create, update, and delete courses in course management) |
| Structure administrator | Manage courses within their layer via inherited structure access |
| Course editor | Edit a specific course, duplicate it, adjust settings inside the course (requires write access on that course’s structure) |
| Module planner / program coordinator | Ensure linked courses align with cohort curricula and module versions |
| Teacher | Delivers inside the LMS course; may edit journey content depending on role |
Exact visibility follows your institution’s roles and permissions design. Two staff members with different scopes may see different subsets of the Courses table. For how permissions combine with feature packages, see Permissions, features and visibility.
Where to start
If you are setting up a new term:
- Confirm institution booking/waitlist policy with an administrator if students self-enroll — see Institution settings overview.
- Browse existing courses to avoid duplicate offerings.
- Create net-new courses or duplicate proven templates from the previous year.
- Edit names, codes, and tags; then open Course settings for features and capacity.
- Link courses to module versions when academic tracking applies.
- Enroll or bulk-enroll students and staff.
- Point teachers to the LMS course experience for delivery.
- Archive offerings when the term ends.