---
title: Publish a bundle
description: >-
  Enable course bundles for your institution and prepare a bundle so it is
  active, unarchived, and ready for user enrollment.
sidebar:
  order: 3
---

**A bundle is ready for learners when Course Bundles is turned on for your institution, the bundle is not archived, its courses are linked, and members are enrolled with Active status or join through an invite link.**

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.

:::info
**Key point:** an institution administrator must enable **Course Bundles** for your institution before bundles appear anywhere in the product. That means both the contracted **Course Bundles** feature **and** the **Course Bundles** institution setting (*Allow grouping courses into bundles and enrolling users in them*).
:::

## 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.

| 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, access duration, linked courses | [Create a bundle](/docs/fuxam-web/lms/course-bundles/create-a-bundle) |
| Bundle active | Not archived in the bundles list | [Edit a bundle](/docs/fuxam-web/lms/course-bundles/edit-a-bundle) |
| Learners have access | Members enrolled with **Active** status | [Enroll in a bundle](/docs/fuxam-web/lms/course-bundles/enroll-in-a-bundle) |
| Students see the programme | **Home → Bundles** tab with bundle details | [Navigate the dashboard](/docs/fuxam-web/lms/getting-around/navigate-the-dashboard) |

Bundles differ from [Book and unbook courses](/docs/fuxam-web/lms/student-home/book-courses), where students self-enroll in individual open courses. Bundle access is assigned by administrators through Campus Management.

## 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. Invite links don't work while a bundle is archived |
| **Access expires at** | Date a member's access ends: the due date (**Fixed date range**) or their own duration after joining (**Individual duration**). Fuxam then removes the membership and the course access it granted |

## How to enable bundles for your institution

1. Confirm the **Course Bundles** feature is included in your institution's contract and turned on by an administrator.

2. 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.

:::note
Some capabilities are part of your institution's contract. The **Course Bundles** institution setting is an additional on/off switch. Both must be active — see [Permissions and features](/docs/fuxam-web/settings/permissions-and-features) for how Fuxam controls which Campus Management sections are available.
:::

## How to prepare the bundle for enrollment

1. Create the bundle with a clear **name**, **description** and **access duration**.

2. Add all required **courses** on the bundle **Courses** page.

3. Confirm the bundle is **not archived**. Switch the bundles list from **Archived** back to **Active** if you previously archived it.

4. Enroll users on the **Users** page with **Active** membership status so they receive course access, or share a free or paid invite link from **Settings** → **Payment** so people can join themselves — see [Edit a bundle](/docs/fuxam-web/lms/course-bundles/edit-a-bundle).

Each underlying course should already exist in [Course management](/docs/fuxam-web/cms/courses-management) and be teachable in the LMS. Bundle readiness does not substitute for course-level setup — journeys, content, and [course settings](/docs/fuxam-web/lms/courses/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.

:::tip
Use **Inactive** to pause a learner's programme access without deleting their membership record — for example, during a formal leave of absence — then return them to **Active** when they resume.
:::

## 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](/docs/fuxam-web/lms/courses) with its own learning journey. Enrollment source appears as **Via Bundle** on course **Users** tabs — see [Assign to users](/docs/fuxam-web/lms/learning-journey/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 Campus Management | Fixed multi-course programmes |
| **Bundle invite link** | User opens a free or paid link the administrator shared | Open offerings, or bundles people pay for |
| **[Bulk-enroll](/docs/fuxam-web/cms/courses-management/bulk-enroll)** | Administrator per course | Many users into one course |
| **[Manage enrollments](/docs/fuxam-web/cms/courses-management/manage-enrollments)** | Administrator per course | Individual adds and removals |
| **[Course booking](/docs/fuxam-web/lms/student-home/book-courses)** | 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 a price without a Stripe recipient.** The **Payment** section only lets you set a price when **Stripe recipient account** shows **Recipient ready**. Free invite links work without one.
- **Access ran out.** Members whose **Access expires at** date has passed lose their membership and bundle-only course access. Enroll them again, or change the access duration before it runs out.

## 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?**

Only through an invite link. An administrator can generate a free or paid invite link on the bundle **Settings** page; whoever opens it joins the bundle (after paying, for the paid link). Otherwise bundle membership is assigned in Campus Management. [Book and unbook courses](/docs/fuxam-web/lms/student-home/book-courses) covers self-service for individual bookable courses, which is a different feature.

## Related pages

**[Create a bundle](/docs/fuxam-web/lms/course-bundles/create-a-bundle)**

Initial bundle setup.

**[Enroll in a bundle](/docs/fuxam-web/lms/course-bundles/enroll-in-a-bundle)**

Add users and set membership status.

**[Assign to users](/docs/fuxam-web/lms/learning-journey/assign-to-users)**

How bundle enrollment flows into course learning journeys.

**[Course bundles overview](/docs/fuxam-web/lms/course-bundles)**

When to use bundles vs individual courses.
