Versions And Publishing

QAVRA separates drafts from learner-ready published versions so admins can review changes before learners receive them.

Key Ideas

Draft is the editable course state. Brainstorming, reviewing, or drafting changes does not affect learners until an admin saves and publishes the right change.

Major publish is for broad course changes, such as a new publish from a blueprint or changes that affect more than objective-only structure.

Minor publish keeps the current major course version and publishes an objective-only update when the draft qualifies. The review dialog shows added, changed, and deleted objectives before an admin confirms.

Restore version lets an admin copy a published version’s objectives back into the draft for review.

When To Use Minor Publish

Use a minor publish when the change is limited to the objective set and QAVRA confirms it qualifies.

QAVRA blocks minor publish when the draft includes fields that require a major publish. In that case, review the blocking fields and use the broader publish path.

  1. Open the course.
  2. Review the current draft and published version.
  3. Make the needed objective changes.
  4. Open the minor version proposal.
  5. Review added, changed, and deleted objectives.
  6. Confirm minor publish only if the proposal matches your intended change.
  7. Use major publish for broader scope, requirement, content, or course-level changes.

Delivery Impact

New learners receive the active published version selected by the course, offering, marketplace listing, or launch setup.

Where a delivery path is pinned to a version, review the offering, LMS, marketplace, or launch configuration before assuming learners will receive the newest version.