Skip to content
zublms
Documentation
Documentation/Create & manage
AvailableLearners, authors, team managers and company administrators

Collections & learning pathways

Curate course discovery, build versioned programmes and follow required milestones without losing existing learning history.

Choose the right experience

Collections gather related published courses for independent discovery. Following a collection saves interest; it does not enrol someone or grant lesson access. Learning pathways are assigned programmes with ordered stages, required and optional courses, deadlines and aggregate progress.

Both are private company workspace features. Public marketing courses are separate. The anonymous demo asks visitors to sign in for real collections and pathways.

Create and follow a collection

Collections reference courses; they do not duplicate content. Course titles and versions reflect the latest publication. Authors can inspect restricted or archived collections for editing. A collection audience controls discovery only; it does not replace existing course enrolment permissions. Archiving hides it from learners while preserving its records.

  1. Open Collections from your workspace navigation. Authors and company administrators can choose Create collection.
  2. Add a title, description and cover colour. Choose everyone in the company or a team and its subteams as the discovery audience.
  3. Choose up to 30 published courses. Drag rows or use the labelled up/down buttons to arrange them. Save with Published enabled to make it discoverable.
  4. Open a collection landing page to browse its ordered course list. Follow it to find it through the Following filter. Open an individual course to view its normal details and access options.

Build a pathway

Every stage must contain a course. A course can appear in many programmes, but only once inside a single programme version. Advanced choose-N electives, automated enrolment rules and pathway certificates are not included in this release.

  1. Open Learning pathways → Create pathway. Add a title, description and cover.
  2. Create up to 12 stages and 60 unique courses in total, with up to 20 courses per stage. Name each stage, choose published courses and mark each required or optional. At least one course across the programme must be required.
  3. Reorder stages and their courses by dragging or using the up/down buttons. Collapse stages to focus. Use Learner preview to inspect the draft without assigning it.
  4. Choose sequential stages or flexible progression. Sequential mode checks required courses in preceding stages; courses within an available stage may be taken in any order. Optional courses never block completion.
  5. Optionally set each stage deadline as days from assignment. Zero means no stage-specific deadline. An earlier overall assignment deadline takes precedence.
  6. Save draft, then choose Publish saved draft in Programme library. Publication pins the exact latest published version of each course. Editing and republishing produces a new programme version; existing assignments keep the previous version.

Completion credit and version rules

  • Earlier completions count only when the author enables credit. At assignment time the system selects completed enrolment cycles for the exact pinned course version, optionally limited to a maximum age in days. Zero days means no age limit.
  • Credit is based on course completion records, not certificate validity or certification expiry. A different course version does not receive automatic equivalence credit.
  • Exact-version completions after assignment count, including independent enrolments. Without prior credit, older completions do not count. An existing active course cycle on the same version can be shared without changing its deadlines. Another active version produces a conflict requiring manager review.
  • Course enrolments are created lazily when the learner starts an available course. Sequential stages therefore do not automatically pre-enrol learners into locked courses.
  • A pathway gate controls access through this programme. It does not revoke independently assigned access to the same course.

Assign and track

Progress is completed required courses divided by all required courses. Optional-only stages have no blocking completion requirement. One non-cancelled assignment per person/programme is allowed. Cancel before creating a replacement cycle; cancellation preserves existing individual enrolments and completed records and stops new pathway launches.

The current views are bounded: 200 collection/programme candidates and the 500 most recent assignment candidates before manager-scope filtering. Counts describe the visible set, not an unlimited company-wide reporting export. Full pagination, scheduled pathway reports and automated notifications are future increments.

  1. Managers open Learning pathways → Assign a pathway, choose a published programme and a person within their authorised scope, and optionally set an overall deadline. The date/time field uses the manager’s device timezone and is stored as an absolute instant.
  2. Learners open Learning journeys and see completed, available, locked and overdue stages. Start or Continue opens the existing course player. Earlier credited completions are labelled.
  3. Managers use the same journey view to inspect learner progress and overdue stages, searching by person or programme and filtering enrolled, started, overdue, completed or cancelled assignments.

API and troubleshooting

These endpoints use the browser session’s organisation and user. Writes also require same-origin CSRF verification. They are not API-key endpoints for third-party integrations. Author, manager, learner ownership and team-scope checks run server-side, with PostgreSQL tenant isolation.

A 409 response means a stale revision, duplicate live assignment or incompatible active course cycle. Reload, review the current version and resolve the conflict; do not overwrite another author’s changes. A 403 may mean changed permissions or a locked stage. Failed saves remain in the editor for correction.

Example JSON payload
GET /api/v1/collections
POST /api/v1/collections
POST /api/v1/collections/follow
GET /api/v1/pathways
POST /api/v1/pathways
POST /api/v1/pathways/publish
GET /api/v1/pathways/assignments
POST /api/v1/pathways/assignments
POST /api/v1/pathways/launch
POST /api/v1/pathways/cancel

Documentation reviewed 3 November 2026 · Current implementation snapshot

Need account help? Contact your company administrator. Planning a rollout? Talk to us.