Forum Discussion
New in Labs: Connected Packages
Connected packages is still in development and will receive updates as part of Labs. Functionality will change over time. Some options could be modified, while others may be removed based on feedback and feature stability. There is no guarantee that Labs experiments will become production features.
The Connected packages feature solves the ages-old headache of keeping your training up to date in your LMS. Now, instead of having to download a fresh package from Rise 360, then uploading it to your LMS every time you make a change, you can deliver updates to your content across LMS environments with just a few clicks.
Connected packages fulfills the dream of publishing once, then dynamically updating your content without re-uploading to your LMS!
Note: Currently, connected packages can only be exported from Rise 360 as SCORM 1.2 and 2004 files.
How to Use Connected Packages
Unlike with standard packages, connected packages let you quickly update your training and notify your learners of changes.
Publishing a Connected Package
Creating a connected package for training content is as simple as creating a standard LMS package.
- Open the content you want to publish from your Rise 360 dashboard. Then click Publish in the upper-right corner of the screen and select LMS.
- Choose an LMS standard. For connected packages, you must select SCORM 2004 or SCORM 1.2 (any edition).
- Select Connected package.
- Toggle the Notify learners option to display a banner to learners when you update the training.
- After selecting any tracking, reporting, and advanced options, click Download.
- Upload the package to your LMS as usual.
Updating a Connected Package
After you’ve published your connected package to your LMS, all future updates happen right in Rise 360.
- When you make changes to your content, an indicator displays on the Publish menu.
- Click either the View Updates button or you can select Connected package from the Publish menu to jump to step 4.
- Select Connected package. If you’ve published your content to Reach 360 or shared with Quick Share, you’ll be able to select those as well.
- Click Update now. Rise handles the rest!
If you toggle or have previously activated the Notify learners option, your learners will see an update banner the next time they refresh or log in to the training.
Note: You can also download a copy of the last-deployed LMS package by clicking Download again.
Notifying Learners of Changes and Resetting Learner Progress
If you update your content and want to notify learners but didn't select the option when you initially published your package, you can enable it when you publish changes.
- In your updated content, click Publish in the upper-right corner of the screen and select LMS.
- Toggle the Notify learners option.
- Click Update now.
With this option enabled, a banner displays for active learners whenever you update the training. Learners who've already completed the training don't receive any notification.
Sometimes, after making updates, you also need to reset learner progress so that active learners don't end up in a blank state when they resume the training. This functionality can now easily be enabled at any time when using connected packages.
- In your updated content, click Publish in the upper-right corner of the screen and select LMS.
- Toggle the Reset progress after updates option.
- Click Update now.
This operates the same as the Reset Learner Progress option in standard packages and does not reset the progress or cancel quiz scores for learners who've already completed the training.
Connected Packages FAQs
When I deploy training to my LMS via Connected Packages, is Articulate the host for my content?
Training deployed to LMS via Connected Packages is hosted on Articulate's systems and is subject to the same security and data policies as other data hosted on the platform, as outlined in our Terms of Service. For additional resources on Articulate's security and data protection, visit our Trust Center.
What content is best suited to connected packages? Is there content I shouldn’t use with connected packages?
Connected packages is best used to deploy content that’s updated frequently or that you plan to iterate on once it’s live.
Since the feature doesn't provide automatic version tracking, we don’t recommend using connected packages with content that requires strict audit trails or enhanced compliance procedures.
Are connected package updates in Rise considered new versions by my LMS?
No, only the files you manually upload to your LMS are considered new versions of the content. Updates you make in Rise are sent to whatever version of the file is currently uploaded to your LMS.
In which regional data center does my content reside?
While regional hosting isn't a consideration at this stage of development, Connected Packages should be available in your regional hosting location when launched for general availability.
What happens when I delete training in Rise that's been deployed using connected packages? Will training work in my LMS if I turn off the Labs feature?
Content deleted from your Rise dashboard will still function in your LMS until you permanently delete the source training. You’ll be able to restore it from the trash and continue to update via Connected Packages without manually uploading a new package to your LMS. When permanently deleted, the connected package is also deleted.
If you disable the Labs feature, all connected packages are deactivated and deleted, but the source content remains untouched.
Permanently deleting associated Rise content or disabling Labs, will cause the training in your LMS to stop functioning. To restore, manually upload a standard package as a new version of the same training.
Can I use the same troubleshooting steps with Connected Packages as I do with Standard Packages?
Yes, while your content is hosted by Articulate, the same troubleshooting steps, such as resetting learner progress and hiding the LMS interface, can still be applied as detailed in the Rise 360 user guide.
Do Connected Packages send information to Articulate from my LMS?
While the Connected Packages feature is in Labs, we use a third-party data subprocessor, Datadog, to track certain information in order to identify and debug issues as they arise. In particular: Course ID, Learner ID (based on the Subscription ID plus an LMS Learner ID, if one is returned by the LMS), and your subscription ID. This information is not captured for every Connected Package.
Additionally, Allow usage data collection is enabled by default for all content exported to an LMS. This option provides Articulate with the course ID launched and non-identifiable learner usage data, as shown in our data collection details. It can be disabled on a per-package basis.
If I collaborate with other creators, can they update training deployed to my LMS?
Only content owners and collaborator managers with the feature enabled can send training updates via Connected Packages.
Can I download packages after initially publishing via connected packages?
Yes. There’s a Download button at the top of the LMS publish screen. Keep in mind that you have access only to the last-deployed version of the package.
Will connected packages be available for other LMS export standards? Is it coming to Storyline 360?
We would love to hear your feedback on what export format you’d like to see next for Connected Packages! And while Storyline support isn’t planned at this time, if it’s something you’d like to see, please let us know.
Share Your Feedback
For this initial Labs release, we want to hear how connected packages perform across real LMS environments and whether the experience feels as intuitive. Your feedback will directly influence development, so consider sharing your thoughts on the following topics:
- Uses: Does the "publish once, update anytime" workflow sync with how you manage training content?
- Bugs. Is anything not working as expected? Do the updates behave as you’d expect with your specific LMS setup?
- Improvements. How could this feature be better? What changes, if any, would you like to see?
- Insights. How does this new publish-to-update workflow fit into your day-to-day?
You can enable and disable this feature from the Labs page in account settings. Share your thoughts in this Labs forum or use the feedback form directly within the feature.
237 Replies
Hoping that if this feature is brought beyond labs that Articulate Admins can turn it off or opt-out for all seats.
This would allow creators to bypass our quality assurance processes (including checkpoints to ensure 508 compliance) which could put our org at risk.Hi Articulate Team,
We are currently testing the new Connected Packages (Labs) feature in Rise 360 with LearnDash, and we love the concept of instant updates across platforms.
In our courses, we use a custom Code Block that allows students to record their voice for spoken practice and pronunciation drills using the browser's MediaDevices API (navigator.mediaDevices.getUserMedia).
The issue we're running into:
- Standard SCORM package: Microphone recording works smoothly because the course runs locally from the LMS server.
- Connected Package: The microphone fails to initialize completely, and the browser console throws: [Violation] Permissions policy violation: microphone is not allowed in this document.
Because Connected Packages stream remotely from packages.articulateusercontent.com, the browser applies cross-origin restrictions, blocking hardware access down to the embedded code block.
We would love to migrate our courses to Connected Packages, but our curriculum depends on student voice recording—and this will inevitably block any creator building language courses, speech exercises, or oral practice from adopting Connected Packages as well.
Since this feature is currently in Labs, is there a plan to delegate microphone permissions (or provide an authoring toggle) in the cloud player environment?
Any insight or workaround would be greatly appreciated!
Thank you for the detailed write-up, and for including the exact console error. That made it easy to see what's going on.
You're right about the cause. Because Connected Package content loads from packages.articulateusercontent.com inside the LMS, the browser needs the microphone permission to be passed down to that content, and today, I am assuming it isn't.
I've shared this with our engineering team to look at how we handle microphone access in Connected Packages, and I'll follow up here once I know more. For now, courses that rely on voice recording should stay on standard packages.
Out of curiosity, does your Code Block use the camera too, or just the microphone?
No. We don't use the camera for this activity.
OMFG, this is gold.... I say gold. So is this working technically as an AICC file? One option that we would love to see or if you have an answer is for versioning, etc...
The part about letting learners know its updated, and can reset the results here rather than in the LMS is such an awesome consideration too. Love this keep it going....
Hi DougKipta-e46cc,
Glad this is landing well!
On AICC: no, Connected Packages currently only export as SCORM 1.2 or SCORM 2004.
On versioning: right now, updates from Rise overwrite whatever file is already in your LMS rather than creating a new version there. For strict audit trails, you'd still want to download and upload a fresh package. More robust version history inside Rise is something we're exploring based on feedback like yours.
The notify-learners and reset-progress toggles were built for exactly this scenario, glad they're resonating. Feel free to share your thoughts with us in our feedback form.
Is there any update for the timeline of this moving from Labs (beta testing) to a permanent feature?
I've recently started using connected packages (beta) on a project I'm working on. We are a SaaS company with frequent changes in our software, and therefore our course content (screen shots, descriptions, not actual course structure). The ability to publish the course to the LMS via a connected package without having to replace the SCORM file is huge for us (so that in-progress learners won't lose their bookmark!) and maintenance-critical. I was having a problem with a survey block recording this week, and found a bug that if a survey block is used, it will not record results in the LMS and was told to go back to the old-fashioned way and just replace SCORM files rather than using connected packages, and connected packages are in beta and are experimental, and it is not recommended to use them in training delivered to users. Disappointing. Anyway, I will turn off connected packages, but what is the best practice if this goes live and we can turn this on eventually and use the feature? I will have a SCORM file uploaded to the LMS, turn on the connected package feature (unless it goes away) when it is ready, and hope for the best? Also, can I receive some clarification on what beta means to Articulate? In software it means pre-release, but Support warned me that the feature may just go away and should not be used live. Thanks for your help.
Hi AmyLNewhook,
Thanks for sharing this, your use case (frequent content updates, stable structure, in-progress learners keeping their bookmark) is exactly what Connected Packages is designed for, and it's great context for us.
On "beta": Connected Packages is a Labs experiment, which means it's still being tested and can change based on what we learn. That's why Support flagged it as not recommended for live learner training right now, not because the feature is broken day-to-day, but because we're still working out edge cases like the one you hit.
On best practice: your instinct is right. Keep a standard SCORM file uploaded as your working baseline, and turn on Connected Packages when you're ready to test further. If something goes wrong, you just re-upload the standard package.
On the survey block: survey data can be reported to your LMS through a Connected Package, it works similarly to quiz results. The difference is that some LMSs need to be configured to listen for this type of data. It's worth checking with your LMS admin to confirm your LMS is set up to capture survey responses, since that configuration step may be what's needed.
I uploaded a course using connected package and after some weeks the course content disappeared on my LMS. Not sure what went wrong but on rise 360 only shown that I have never exported a course on connected package and I had to export the connected package option again.
Is it something common other usersHello LimaMaria,
Thanks for flagging this. What you described isn’t the expected behavior for a Connected Package.
A Connected Package should remain connected to the source course in Rise 360. One thing that can affect that connection is disabling the Connected Packages experiment in Labs, which deactivates connected packages.
Do you know if the Labs feature may have been disabled at any point, or if the original Rise course was duplicated or moved? If not, I’d like to have our Support team take a closer look at what happened within a support case.Hi LucianaPiazza
I dont believe I disabled it at any point or duplicated it.
What I did is that I shared the course with a teammate making him a manager under the collaborators so he could also edit the connected package.
Let me know if that is something not reccomended or if I should still talk with support case
This is a critical feature! thanks!
Is reset progress necessary in connected packages?
I uploaded a connected package to my LMS and after an update I made, all "Continue" buttons at the end of my lessons disapeared from the training, and I had to do "reset progress" via the LMS, so they appear again.Hello OfriSheferGilat,
Great question! Resetting learner progress isn’t necessary for every Connected Package update.
It becomes important when an update changes the structure of the course, such as adding or removing lessons or quizzes, since an active learner’s saved progress may no longer line up with the updated structure.
Since your Continue buttons disappeared after the update, I’d be curious to know whether you made any structural changes to the course at the same time. Also, which LMS are you using? That context would be helpful as we continue testing Connected Packages.
Thanks for sharing this update. We're really excited about the idea behind Connected Packages, and I can see it being incredibly useful for managing course updates.
I do have a question about how learner progress is handled when a course is updated.
For example, if I have an eight-lesson course and a learner completes six lessons before leaving the course, then I make a small change to Lesson 3 and republish it, what happens when they return to complete the final two lessons?
- Will the course still register as complete?
- Will Lesson 3 be treated as incomplete because it was updated after they viewed it?
- Would they need to revisit Lesson 3 for their progress to reach 100% again?
The reason I ask is that we've had a few cases where learners appear to have completed a course, but completion hasn't been passed back to our LMS. I'm wondering whether updates made while someone is partway through a course could be playing a part.
Some of our courses are fairly long, and learners often dip in and out over days or weeks, so I'm keen to understand the impact of publishing updates without disrupting progress for those already working through a course.
I'd be really interested to hear how Connected Packages handle this scenario.
Thank you!
Hi KatieNoble,
Thanks for laying out that scenario so clearly!
If you’re making a small content change within an existing lesson without changing the course structure, the learner’s existing progress should remain intact. In your example, updating content within Lesson 3 wouldn’t normally cause that completed lesson to become incomplete or require the learner to revisit it.
Structural changes, such as adding or removing lessons or quizzes, are where Reset Learner Progress may be needed for active learners.
Since you’ve also seen cases where learners complete the course but completion isn’t passed back to your LMS, I’d recommend testing that behavior separately as well. If you continue seeing it, our Support team would be happy to help determine whether the issue is related to Connected Packages, the LMS, or the course’s completion settings.If you don't make structural lesson changes it should be OK.
It would be good to benchmark what your existing SCORM completion issue rates in the LMS is for these large/long duration in-progress courses, to be able to separate apples from apples when adding Connected Courses into the mix.
For your scenario:
- Version 1, 8 lesson course, in-progress learner is at lesson 7 resume point (lessons 1-6 complete, 6/8 = 75%).
- Version 2 is published without structural changes to the course/lesson count, but minor content within lesson 3 is new (75% lesson completion remains in version 2).
- Learner completes version 2 lesson 7 and 8 (75% => 100%) to register course completion reported to LMS at 100%.
Rise360 completion article for reference below:https://www.articulatesupport.com/article/Rise-360-When-a-Course-Communicates-Completion-to-an-LMS
I am not able to get full screen video through video block or Storyline 360 block with this. I am using Workday as my LMS. I assume it might have something to do with that but not sure. Basically, the full screen button does nothing when you press it.
EpicEdward Closing the loop here for anyone reading later: fullscreen for Video blocks is fixed, and Edward confirmed it's working in his thread after refreshing his package. If you downloaded your package before August 18, make a small change to your course, click Update, then Download Package again and re-upload it to your LMS. Fullscreen for Storyline blocks is still a known issue with a fix in progress that we hope to have out very soon.
Hi EpicEdward,
Thanks for testing this in Workday!
The fullscreen issues you’re seeing with Storyline and video blocks in Connected Packages are both known limitations that we’re actively tracking.
In the meantime, if fullscreen is essential for your learners, the current workaround is to publish your content as a standard SCORM package.
This feature is AMAZING. We have waited so long for this and it is going to save us so much time!!
I know since it's still being tested, we have no guarantee - but if something were to change or be removed, any idea what it might be? We have been using the connected package feature sparingly, but I would love to use it more. However, I want to make sure we don't rely on it too much and then have it disappear.... Any idea of current complaints with it? Anything giving negative results that might need to change?
JamieDerry-a295 Just catching up here, thanks @42HAL9k for pointing Jamie in the right direction!
Jamie, the exit button issue has been fixed. Packages downloaded before mid-September need a refresh: make a small change to your course, click Update on the existing connected package, then Download Package again and re-upload it to your LMS. If you're still seeing an error after that, let us know which LMS you're using.Hi JamieDerry-a295,
Love hearing how useful Connected Packages has already been for your workflow!
Since Connected Packages is still a Labs experiment, I don’t want to speculate about which parts may change or make promises about its future availability. Labs features can continue to evolve based on testing, feedback, and feature stability.
That said, the feedback you’re sharing is exactly what helps the team understand how people are using it and what they need before relying on it more broadly. If there are particular workflows you’re hesitant to move over because of that uncertainty, we’d love to hear about those too.A staff member confirmed the feature will be adopted permanently, using a course exit button was a known bug staff replied to, the ETA was possibly late October but pending official roadmap announcement.
