Edit a bundle
Update a course bundle name, description, date range, linked courses, and archive or restore bundles in OrgHub.
After a bundle exists, its detail pages are where you keep metadata, course membership, and configuration aligned with how the programme actually runs. Editing a bundle does not change the content inside member courses — teachers still update learning journeys and materials inside each course — but it does control which courses belong to the package and whether enrolled users follow those changes.
Why it matters
Programmes evolve. A course is added mid-stream, a title is corrected for students, or an intake’s dates shift. Without a maintained bundle record, enrollment drift appears: some learners have four of five courses, others still see an outdated name on Home → Bundles, and administrators cannot tell which enrollments came from the bundle versus direct course assignment.
Keeping the bundle accurate preserves a single source of truth for the programme shell while each member course remains independently teachable.
How it fits
| Task | Where in the bundle | Related handbook |
|---|---|---|
| Change programme label or window | Settings | This page |
| Adjust which courses are in the package | Courses | Courses for per-course teaching setup |
| Add or remove learners | Users | Enroll in a bundle |
| Hide an ended programme | Bundles list archive action | Publish a bundle |
Key concepts
| Concept | What to know |
|---|---|
| Bundle only | Changes the bundle record without altering existing course enrollments for current members |
| Bundle and course | Propagates the change so enrolled members also gain or lose course enrollment |
| Archived | Bundle hidden from the active list; unarchive to restore |
| Deleted | Permanent removal; users lose access to courses they had only through that bundle |
How to open a bundle
Go to OrgHub → Management → Course Management → Bundles.
Click the bundle name to open its detail view.
The detail view provides Courses, Users, and Settings pages for ongoing maintenance.
How to update name and description
Open the Settings page for the bundle (or use Edit Bundle from the list actions).
Change the name or description.
Save. A success message confirms Bundle settings saved.
You can also update the date range when editing bundle metadata. The start date must remain before the due date, consistent with bundle creation rules.
How to manage courses in the bundle
Open the Courses page for the bundle.
Click Add Courses, select existing courses, and confirm.
When members are already enrolled, choose whether to Add to bundle only or Add to bundle and enroll users in course.
To remove courses, select them and confirm. Choose Remove from bundle only or Remove from bundle and remove users from course when prompted.
Add or remove options explained
| Option when adding | Effect |
|---|---|
| Add to bundle only | New courses join the package definition; existing members are not automatically enrolled in those courses |
| Add to bundle and enroll users in course | New courses join the package and current bundle members receive enrollment in those courses |
| Option when removing | Effect |
|---|---|
| Remove from bundle only | Course leaves the package definition; members keep enrollment in that course if they already had it |
| Remove from bundle and remove users from course | Course leaves the package and members lose enrollment in that course when their only access was through this bundle |
How to archive a bundle
From the bundles list, select one or more bundles.
Use the archive action to hide them from the active view.
Archived bundles appear when you switch the list filter to Archived. Unarchive restores them to the active list. Archiving is appropriate when a programme intake has ended and you no longer want the bundle in day-to-day administration — see Publish a bundle for how archive state relates to enrollment.
Best practices
- Prefer “bundle only” when testing lineup changes. Add a course to the bundle definition first; propagate enrollment once you confirm the course is ready for learners.
- Use “bundle and course” when mid-programme additions must reach everyone immediately. Typical when a mandatory module is added to an active certificate cohort.
- Document propagation choices for your team. The add and remove prompts are the main lever for keeping bundle membership and course enrollments in sync.
- Archive instead of delete when historical records matter. Deletion is irreversible and strips bundle-only access.
Common pitfalls
- Removing a course without understanding propagation. Remove from bundle and remove users from course can unintentionally drop learners from a course they still need to finish.
- Editing dates without checking student visibility. Learners see the bundle date range on Home → Bundles; sudden changes can confuse programme expectations.
- Assuming archive removes course enrollments. Archiving hides the bundle from the active admin list; review Enroll in a bundle and membership status for access implications.
- Forgetting per-course setup. A course added to a bundle still needs its own journey, staff, and settings in the LMS — the bundle does not configure teaching content.
FAQ
What is the difference between archive and delete?
Archive hides the bundle from the active list and can be reversed by unarchiving. Delete permanently removes the bundle and revokes course access users had only through it.
Can I edit a bundle while users are enrolled?
Yes. Name, description, dates, and course membership can all be updated. Course add and remove actions prompt you to choose how changes affect existing members.
Where do I see bundle-sourced enrollments in a course?
On each linked course Users tab, the Added From column shows Via Bundle with the bundle name. See Assign to users.