Blog Post

Articles
2 MIN READ

Say Goodbye to Re-Uploads: Update Your LMS Content Directly from Rise 360 with Connected Packages

CommunityTeam's avatar
3 months ago

We're excited to introduce Connected Packages, a new, more modern way to publish and maintain LMS content directly from Rise, is now available in Labs.

What Is Connected Packages?

Connected Packages is a new LMS publishing method that lets you upload content once and maintain it without repeating the full publish-and-upload process.

If you’ve experienced the process of updating a course that’s already in your LMS, whether it’s addressing a simple typo or transforming the entire content, you know the hassle. Re-exporting the package, downloading, and re-uploading it to your LMS, all while handling version updates. It works, but for teams maintaining many courses, it creates real overhead.

Connected Packages changes that workflow.

Instead of bundling your full course into a static file every time something changes, Connected Packages allows you to upload a lightweight LMS package to your LMS once. Your course content is hosted by Articulate and delivered to learners when they launch from the LMS. When you need to make updates, just modify the hosted content; there's no need to re-export and re-upload the whole package from scratch.

It works with your existing SCORM-based LMS workflows, so there's no overhaul required. Just a simpler, more efficient way to keep your training current.

When to Use Connected Packages

Connected Packages is a great fit for teams who:

  • Maintain courses that need frequent updates
  • Work with media-rich or large courses where file size has been a friction point
  • Manage large libraries of LMS-delivered content
  • Want to reduce the repetitive work of exporting and re-uploading whenever something changes

If your team's goal is to keep training accurate and up to date without adding more operational overhead, this was built with you in mind.

A Few Things to Know

Connected Packages is launching in Labs, which means we're still building out the full feature set. For now, robust version history isn't yet supported. If your workflow requires tracking every course version tied to a specific learner record for audit purposes, traditional LMS publishing is still the right fit for that use case. We'll keep improving Connected Packages based on your feedback as we move through Labs.

🎥 Tip Video: Demo Video: How to Publish with Connected Packages

Try It Out!

To learn more about Connected Packages and be a part of the Labs testing, head on over to New in Labs: Connected Packages today.

We Want to Hear From You

💬 Have you tried Connected Packages yet? We'd love to hear how it fits into your LMS workflow — share your questions, early experiences, and use cases in the comments below!

Published 3 months ago
Version 1.0

15 Comments

  • GentryRuley's avatar
    GentryRuley
    Community Member

    Any plans for xAPI exports to be supported for Connected Packages?

    • MaryEmma_Gary's avatar
      MaryEmma_Gary
      Staff

      Hey GentryRuley​ that's a great question! The roadmap for this is being established based off customer feedback, so if you'd like to see xAPI for connected packages I would recommend submitting it to the ideas group. 

  • This is SO great, I am thrilled! This streamlines a huge aspect of my work - thank you!

  • This is great! How is the load balancing with the Connect Packages compared to standard SCORM packages? Has there been any testing on a large number of users accessing the content from a Connect Package at the same time, and is there any performance degradation? Thanks!

    • MaryEmma_Gary's avatar
      MaryEmma_Gary
      Staff

      Hi KristinSwintek​, these are great questions! If you're not already part of the Labs group, they could really use these types of inquiries. you can check out the full Labs thread on Connected Packages here.

      catganim​ might be able to let you know more about the tests done! 

    • catganim's avatar
      catganim
      Staff

      KristinSwintek​ Thanks for the question! Our system is designed for scale and we don't have any current concerns about handling the load you might throw at a connected package. 

  • Hi, does this means the scorm package is actually hosted on Articulate side instead of the LMS?

    • CydWalker_mwh's avatar
      CydWalker_mwh
      Community Member

      I noticed this in the article, not sure if this answers your question?

      Instead of bundling your full course into a static file every time something changes, Connected Packages allows you to upload a lightweight LMS package to your LMS once. Your course content is hosted by Articulate and delivered to learners when they launch from the LMS. When you need to make updates, just modify the hosted content; there's no need to re-export and re-upload the whole package from scratch.

      • tmudavid's avatar
        tmudavid
        Community Member

        Will a connected package continue to push the last published version of a Rise course even if the course owner's Articulate subscription has lapsed?

  • Hey tmudavid​, 

    Great question.

    Training deployed to LMS via Connected Packages is hosted on Articulate systems and is subject to the same data retention policies as other data hosted on our platform. As outlined in our Terms of Service.

    If a subscription lapses, the Connected Package may continue to serve the last published version for a period of time. However, we can’t guarantee long-term, continued access after a subscription ends. Once the hosted course content is no longer available, the Connected Package in the LMS will no longer be able to launch that content. For that reason, we recommend maintaining an active Articulate subscription for any Rise courses being delivered through Connected Packages.

    Please let me know if I can help with anything else!

    • tmudavid's avatar
      tmudavid
      Community Member

      That's very helpful to know, thanks! A quasi-related follow-up...

      • Rise allows authors to embed Storyline blocks via Review 360.
      • When the Rise course is exported as a traditional SCORM package (not a "Connected Package"), does the published Storyline project get fully included within the SCORM file? Can it run smoothly without a connection to Review 360?
      • Would anything happen to the Storyline block within the traditional SCORM package if the author's subscription ended and the source Review 360 link was deleted?
  • You're welcome, tmudavid​!

    When you export a Rise course as a standard SCORM package, the published Storyline Block is included in that package. Although the Block is initially added to Rise from Review, the exported course doesn’t reference or load the Storyline content from the original Review link.

    The Storyline Block will continue to work normally in the LMS without a connection to Review. If the author’s Articulate 360 subscription ends or the source Review item is later deleted, it won’t affect an already exported and deployed standard SCORM package.

    Please keep in mind that the original .story project file isn’t included in the SCORM output. If you ever need to update the course, you must edit that source file. Then publish the updated version to Review, update the Storyline Block in Rise, and export a new SCORM package.

    This behavior differs from a Connected Package, which hosts the Rise course through Articulate servers and relies on that hosted course remaining available. 

  • Is there a document/page that I can send to our IT team which outlines how this connection works and any security in this connection? 

  • Hey MelissaHargis-2​, 

    Thanks for reaching out.

    We're currently preparing public documentation, as Rise Connected Packages are still in development. The feature continues to receive updates, and functionality may change over time.

    If you and your team have specific questions, feel free to share them in our dedicated megathread.