Search documentation

Search documentation pages and headings.

Skip to content

Learning content · How-to guide

Collections

Group ordered courses into programs and track learner progress.

Collections group courses into an ordered learning program. Use them for onboarding paths, compliance programs, customer education, or any workflow where learners should receive several courses together.

Create a Collection#

  1. Open Admin > Collections.
  2. Select Create Collection.
  3. Enter a name and description.
  4. Save the collection.
  5. Open its Courses tab to add content.

The language selector in the admin header controls the locale you are editing. Localize the collection name and description for every language you offer.

Add and Order Courses#

From the collection's Courses tab, you can:

  • Add one or more existing courses.
  • Drag courses into the order learners should see them.
  • Remove a course from the collection.

Removing a course from a collection does not delete the course. The course remains available in Admin > Courses and may still have direct learners or belong to other collections.

Before inviting learners, verify that every course has a valid SCORM module in each required locale.

Give Learners Access#

Collection access is managed in the same way as course access:

  • Invite learners by email.
  • Copy and distribute the public collection link. Learners without an existing invitation use it to request access.
  • Review learner requests and accept or reject them.
  • Remove learners who should no longer have collection access.

When a learner joins a collection, its courses appear inside the collection in the learner portal. Their access to those courses is inherited from the collection, so you do not need to invite them to every course separately.

Learners can accept or reject invitations. They can also leave a collection, while administrators can review active learners, invitations, and requests from the collection or organization learner views.

Track Collection Progress#

Collection progress is derived from the learner's course attempts. Kokobi tracks:

  • The total number of courses.
  • How many courses the learner has started.
  • How many courses the learner has completed.
  • An overall status of not-started, in-progress, or completed.
  • The collection completion date, when applicable.

The collection overview also shows aggregate course and learner counts. Open the Learners tab for individual progress.

Collection progress uses terminal course attempts. The statuses completed, passed, and failed all count as finished for aggregate collection progress, so review individual course statuses when success matters.

Plan Collection Changes#

Changing a live collection affects the program learners see:

  • Adding a course increases the work required to complete the collection.
  • Removing a course removes it from the collection path but does not erase the learner's course attempt.
  • Reordering courses changes presentation order; it does not reset progress.

Make structural changes before inviting learners when possible. If you change an active program, communicate what changed and review completion reporting afterward.

Archive or Delete a Collection#

Archive a collection when it should no longer appear in normal administration or enrollment workflows. Archived collections can be restored.

Deleting a collection is permanent, but it does not delete the independent courses that were included in it. Archive first if you may need the collection configuration or learner relationship history later.