2.4 Publishing Courses & Version Control

Modified on Tue, 8 Jul at 11:20 AM

Publishing in LAAMP makes your training content available to learners. Whether you’re releasing a new course or updating an existing one, understanding LAAMP’s version control system ensures smooth rollouts and proper recordkeeping.


This page explains how publishing works, how version control is handled, and how to manage changes effectively.


Publishing a Course


Courses must be published before they become available to users.


To publish a course:

  1. Ensure it includes at least one Chapter and one Page.

  2. Assign the course to a Location.

  3. From the course editor, click “Publish” in the top-right corner.


Once published:

  • Users assigned to the relevant Location can access it immediately.

  • It becomes visible in the Course List and available for Competency assignment.


Save as Draft vs Publish

  • Save as Draft:

    Allows you to build or edit the course without affecting the live version. Use this when you’re still designing content or making revisions.

  • Publish:

    Makes the current draft the new active version. Users will complete this version going forward.


Editing an Existing Course


When a published course is edited:

  • A new draft version is created behind the scenes.

  • The current published version remains live until you Publish the new draft.

  • Drafts can be reviewed, tested, or edited collaboratively before going live.


Reissuing a Course


When content updates are significant, you may want to reissue the course to users—especially for compliance-critical content.


You have two options:

  • Publish Only:

    The updated version is live for new users. Those already marked as “Competent” do not need to retake it.

  • Publish & Reissue:

    All users, including those who previously completed it, are assigned the updated course again. A “Reissued” badge is shown.


Version History


LAAMP maintains a record of all versions published, including:

  • The user who published it

  • The date/time of publication

  • Whether it was reissued

  • Any linked evidence and completions tied to that version


This helps you demonstrate due diligence and maintain training compliance over time.


Best Practice Tips

  • Always Save as Draft while editing to avoid unintentional changes going live.

  • Use Publish & Reissue when legal, regulatory, or safety-critical changes are made.

  • Inform your team or users when major changes are published—especially if their learning status will reset

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article