Create a bundle for a client
A bundle groups one or more courses under a single client, and it's what participants are usually assigned to rather than a single course — for a self-paced online path or an in-person attendance event. This walks through creating one and what each tab in the editor is for.
BEFORE YOU START
You need a client already set up. A bundle always belongs to one client, and there is nowhere to create one without going through that client's record first.
Create the bundle record
Like a course, a bundle starts with almost nothing — a name and a client. Everything else happens afterwards in the editor.
Open the client's record and go to its Bundles page, then choose New Bundle. Every bundle across every client is also listed under All Bundles in the sidebar, but you always create one from a specific client.
In the dialog, enter a Bundle Name and, optionally, Bundle Information — a short description participants see — then choose Create Bundle.
You land in the bundle editor, which has five tabs: Bundle Details, Courses in Bundle, Certificate, Webhooks and Attendance. Each one saves on its own.
Set the basics on Bundle Details
This tab opens on the bundle's default language. A few fields here decide what participants actually see before they start.
Set the Public Language — English, Deutsch or Français. This is the language shown on the bundle's login screen and dashboard, and must match a translation file — it has nothing to do with your own dashboard language.
Confirm the Name and write Bundle Information in the rich-text field — this is what a participant reads before deciding to start.
If some participants won't have an email address, turn on Enable Phone Login or Enable Guest Login as needed, then choose Save Changes.
Either way, participants who sign in with phone or guest login will not receive email notifications when a course expires or when they check in at a location, since there's no address to send to.
What the other tabs are for
Courses in Bundle is where you add the courses that make up the bundle — covered in the next article. Certificate assigns what a participant receives once every required course is done. Webhooks lets another system know about logins and logouts. Attendance turns the bundle into an in-person check-in event, with its own locations and check-in fields. All five save independently, so switching tabs never loses unsaved work on another one — it just doesn't save it either.
GOOD TO KNOW
All Bundles, in the sidebar, lists every bundle across every client in one place — useful for finding one quickly without opening the client first, even though creation itself always starts from a client.
A COMMON MISTAKE
A freshly created bundle has no courses in it. Sharing its link at this point sends participants to an empty dashboard — add at least one course on Courses in Bundle before handing out the link.
If something isn't working
What next
A bundle with nothing in it doesn't do much. The next step is filling it with courses.