Publish a bundle
Enable course bundles for your institution and prepare a bundle so it is active, unarchived, and ready for user enrollment.
In Fuxam, “publishing” a bundle does not mean clicking a separate Publish button. A bundle is available for enrollment when your institution has bundles turned on, the bundle itself is active (not archived), includes the courses you intend to offer, and members are enrolled with Active status.
Why it matters
Bundles are optional and must be switched on at the institution level. If the Course Bundles feature or institution setting is off, the Bundles tab never appears — and staff may assume the product lacks the capability entirely. Even with bundles enabled, a bundle missing courses, still archived, or full of Inactive members will not deliver the programme experience students expect.
Understanding the publish model prevents false starts: teams create bundles that nobody can see, or enroll users before the course lineup is final.
How it fits
| Stage | What must be true | Handbook reference |
|---|---|---|
| Institution enabled | Course Bundles feature and Course Bundles institution setting both turned on | Below |
| Bundle defined | Name, description, date range, linked courses | Create a bundle |
| Bundle active | Not archived in the bundles list | Edit a bundle |
| Learners have access | Members enrolled with Active status | Enroll in a bundle |
| Students see the programme | Home → Bundles tab with bundle details | Navigate the dashboard |
Bundles differ from Book and unbook courses, where students self-enroll in individual open courses. Bundle access is assigned by administrators through OrgHub.
Key concepts
| Term | Meaning |
|---|---|
| Available for enrollment | Bundle is unarchived, bundles are enabled for your institution, and the bundle is administratively ready for members — not a separate product status |
| Active membership | Member status that grants access to all linked courses |
| Inactive membership | Paused membership; revokes bundle-granted course access for courses the user only had through this bundle |
| Archived bundle | Hidden from the active bundles list; switch filter to Archived to view or unarchive |
How to enable bundles for your institution
Confirm the Course Bundles feature is included in your institution’s contract and turned on by an administrator.
Turn on the Course Bundles institution setting — Course Bundles (Allow grouping courses into bundles and enrolling users in them).
Without both, the Bundles tab and enrollment actions are hidden.
How to prepare the bundle for enrollment
Create the bundle with a clear name, description, and date range.
Add all required courses on the bundle Courses page.
Confirm the bundle is not archived. Switch the bundles list from Archived back to Active if you previously archived it.
Enroll users on the Users page with Active membership status so they receive course access.
Each underlying course should already exist in Course management and be teachable in the LMS. Bundle readiness does not substitute for course-level setup — journeys, content, and course settings still live in each member course.
Active vs inactive membership
Each bundle member has a membership status:
| Status | Effect |
|---|---|
| Active | User has access to all courses in the bundle (subject to course-level rules). |
| Inactive | Membership is paused; bundle-granted course access is revoked for courses the user only had through this bundle. |
Setting a member to Active after enrollment is how you effectively “turn on” access for that user. There is no separate bundle-level publish toggle beyond remaining unarchived and enrolling members as active.
Student visibility
Once enrolled with active membership, students see the bundle on Home → Bundles with its date range, responsible contacts, and linked courses.
Students open individual courses from the bundle overview or from their wider course list. Each course remains a full LMS course with its own learning journey. Enrollment source appears as Via Bundle on course Users tabs — see Assign to users.
If no bundles are assigned, the empty state reads No bundles yet.
Bundles vs other enrollment paths
| Path | Who drives it | Best for |
|---|---|---|
| Bundle enrollment | Administrator in OrgHub | Fixed multi-course programmes |
| Bulk-enroll | Administrator per course | Many users into one course |
| Manage enrollments | Administrator per course | Individual adds and removals |
| Course booking | Student self-service | Elective or bookable module courses |
Best practices
- Enable bundles before communicating them to staff. Avoid training teams on a Bundles tab that is not yet visible.
- Finalise the course list before bulk enrollment. Adding courses later is supported, but you must decide whether changes propagate to existing members.
- Enroll with Active status intentionally. New members receive course access on enrollment; confirm Inactive is only used when pausing access on purpose.
- Archive ended intakes. Keeps the active bundles list manageable without deleting historical records.
Common pitfalls
- Only one of the two settings enabled. The contracted feature alone is not enough — the Course Bundles institution setting must also be turned on.
- Assuming a Publish button exists. Readiness is a combination of archive state, course lineup, and active membership — not a single toggle.
- Archived bundle with active members. Unarchive or confirm whether learners should still see the programme on Home → Bundles.
- Expecting payment integration. Payment configuration for bundles is not yet available in the product.
FAQ
Is there a draft state for bundles?
Fuxam does not label bundles as Draft or Published. A created bundle is administratively editable immediately; learners receive access when enrolled with Active membership and the bundle is not archived.
Does publishing a bundle publish course content?
No. Each member course has its own content and learning journey. Bundle readiness only controls coordinated enrollment and the student bundle overview.
Can students enroll themselves in a bundle?
Not through the bundle mechanism described here. Book and unbook courses covers student self-service for individual bookable courses. Bundle membership is assigned in OrgHub.