Unit Versioning

Publishing a unit locks its structure to protect active student records — but training content still needs to evolve.

Versioning allows you to work on updates in the background. You can create a "Draft" version of an existing unit, make your improvements, and only push them live when you are ready. This ensures a seamless transition from one version of a training package to the next.

What's Covered in This Article

This article explains how to manage the lifecycle of a unit from its initial creation through to its eventual retirement.

Key Concepts: The building blocks of unit versioning.
The Unit Lifecycle: How a unit moves through Draft, Published, and Inactive states.
Updating a Published Unit: How to create and publish a new draft version.
Version History: Viewing past versions for curriculum management and compliance.

Key Concepts

Root Unit: The parent container that holds all historical and current versions of a unit.
Draft Version: A work-in-progress update that is invisible to students until published.
Published Version: The active version currently being delivered to classes.
Inactive Version: An older version that is retained for audit and continuity purposes but is no longer assigned to new classes.

The Unit Lifecycle Workflow

Understanding the status of your unit is essential for curriculum management. A unit moves through three stages: Draft → Published → Inactive

Draft: Every unit begins as a draft. In this state, you can freely add sections, map content, and configure prerequisites. No students can access the unit until it is published.
Published: Once you click Publish, the unit goes live and can be mapped to a course and assigned to classes. At this point, you can no longer add or remove content items or sections, or modify prerequisite settings. Note that certain item-level settings may still be editable; however, the overall structure and content mapping of the unit is fixed..
Inactive: When a newer version of a unit is published, the previous published version moves to an inactive state. It remains in the system so that students already enrolled can complete their work, but new classes will receive the latest version.

Updating a Published Unit

Creating a New Draft Version

If you need to update a unit that is already live (e.g., adding a new video or changing an assessment task), follow these steps:

Open the unit from your Units registry.
Locate the version bar at the top, which will display Current Version V.1.
Click the + Add Draft Version button.
Nimbu will create a duplicate of the current unit (marked as Draft Version V.2).
Make your edits within this draft version. Your changes are not visible to students until you publish.

What Happens When You Publish V.2?

When you are ready to make your draft live, click to Publish button:

New Classes: V.2 becomes the current version. Any new classes created after this point will use V.2.
Existing Classes: Classes already running on V.1 are not affected. Students in those classes will continue to see and complete V.1 until they finish the unit, ensuring their assessment journey is not interrupted.
Previous Version: V.1 moves to an inactive state. It remains accessible for students currently enrolled in it, but will not be assigned to any new classes.

Version History

You can always view the full history of a unit to see how it has evolved over time.

Accessing History: Within the Unit Settings, the version bar allows you to toggle between the current version and any archived or inactive versions.
Audit Trail: This history is vital for compliance, allowing you to show auditors exactly what content was being delivered on any specific date in the past.

Publishing a Unit
Managing Units