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.
268 Replies
- meparkerCommunity Member
Is there any update for the timeline of this moving from Labs (beta testing) to a permanent feature?
- DougKipta-e46ccCommunity Member
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.
- hadassahschecteCommunity Member
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!
- catganimStaff
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?
- hadassahschecteCommunity Member
No. We don't use the camera for this activity.
- ShannonMille321Community Member
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.- catganimStaff
Hey ShannonMille321 thanks for flagging this and explaining the risk to your QA and 508 checkpoints. I've reached out to you directly by email to talk through options for your team.
- Donna_GCommunity Member
I am loving the feature and was wondering when it will be confirmed that it will be out of beta and be a permanent feature as I would like to utilise with a customer.
We have courses that we usually distribute via our own LMS but want to offer a license type for people to use within their own LMS. This has always been on the backburner as we always had the problem that once we hand over the published SCORM file, we lose control over that content and they can just continue to access forever with no way of us to be able to enforce ongoing licensing fees - Connected packages will solve this problem as we can just remove it if they choose not to continue with the subscription.
I have seen above that it is recommended to duplicate the course so you have versions for Customer A, Customer B etc so this can be managed which makes perfect sense but my question around this is whether there is, or could possibly be looked at as a feature, a way to link the content in the duplicate courses to what would effectively be a 'master' version?
This way if you had to make a change it could be reflected across all customers without having to update each one which could get difficult if you had lots of customers (which we would love to expand to).
- catganimStaff
Hi Donna_G, thanks for sharing this, it's a really interesting use case. Today the workaround is the one you described: duplicate the course for each customer. There's currently no way to link copies to a master version. I'm looking into this more, and it would help to know roughly how many customers you'd set up this way, and whether each one would need any differences in the content.
- Donna_GCommunity Member
Hi catganim, At this stage we only have 2 customers that we run this way so not a big issue at all but was just thinking future into the future as we have now got our training platform to a level where we are about to start really promoting it so I would love to think that we could grow this number a lot.
Content itself would remain the same across all customers but we do offer the option of customising their training to match their branding so colours and fonts may change but this would just draw from the theme settings as usual.
- MITOLearningDesCommunity Member
A useful benefit of connected packages is that they can help us avoid LMS file-size limitations. We can remove the videos before exporting and uploading the connected SCORM package, then add them back into the Rise 360 course and republish it. This keeps the initial SCORM package within the upload limit while allowing the connected package to function as intended.
- catganimStaff
MITOLearningDes Hi again! Can you help me understand why you can't include the video in the initial Connected Package? You should be able to include the video in the first pass and bypass the upload limit, all the assets would be stored on our CDN.
- MITOLearningDesCommunity Member
Thanks for the explanation catganim . We upload our own video files directly into Rise 360 rather than embedding content from YouTube. With a standard SCORM export, the videos increased the package size beyond our LMS upload limit.
I’ve now checked the connected export from the same course and found that it is significantly smaller than the standard SCORM package. Am I correct in understanding that uploaded video files are hosted on the CDN and are not included in the connected package in the same way as they are in a standard SCORM export?
- astmartin1Community Member
What a time saver! How does this affect localization credits? If I extensively edit a translated course published through connected packages - does it use locatization credits to update the course?
- catganimStaff
astmartin1 The creation process inside Articulate remains the same, so if you need to translate your course, yes, it would use localization credits. Upon exporting the Connected Package you can select which languages to include when learner's launch the course.
- astmartin1Community Member
Thanks for the reply. To clarify, I am asking if localization credits are used if I were to edit an already translated and exported, live connected package course. For example, we make annual edits to a translated course, these edits can at times be extensive (adding a module, making section changes), would making these changes to a connected package use localization credits?
- AmyJones-f6dfa6Community Member
This is such a brilliant update and saves so much time for my team! If this could be applied to Storyline courses in the future, that would be amazing.
- catganimStaff
AmyJones-f6dfa6 This is something we're actively investigating and I'm hoping you'll hear more about it in the coming months.
- RichardEkparianCommunity Member
Hello!
Thank you for this Rise innovation! We have a home-grown LMS, and republishing a course was always fraught with trepidation. An edited course might work perfectly in our STAGE environment, only to somehow become corrupted when published to Production. It happened often enough that we generally avoided editing published courses. With limited IT resources and little time to troubleshoot what was clearly an issue on our end, the arrival of connected packages is a major boon!
After extensive testing in STAGE, we’ve just published our first connected package to Production. We had a slight hiccup with Akamai blocking the content, but that was quickly and happily resolved. The course includes several code blocks and even some Storyline blocks with embedded video, and everything works normally. So happy!
And now I realize we’re going to have to rethink how we approach course updates. We’re in a fast-changing industry, and I believe connected packages will allow us to keep pace and update our courses much more quickly and confidently.
Thanks again! Richard
- catganimStaff
RichardEkparian thank you for the positive feedback! Glad it's going smoothly so far :)
- catganimStaff
Hi everyone! 👋 Three updates for you:
1. I'm very excited to let you know that we're headed towards general availability for Connected Packages either next week or the week after.
2. We've heard from a few folks that "updates don't stick" (meaning you click update and nothing changes in your course) and we are working on a fix for that and I'll share an update when that fix goes out.
3. Lastly (and where I would love some help), we've just rolled out a more permanent fix for the exit button and exit link, along with a fix for fullscreen in Storyline blocks and videos. These should work with the Connected Package you already have in your LMS, so please try again with whatever package you have before downloading a new one.
If you've run into either issue before, give it another go:
- Exit the course with the Exit course button or link
- Try fullscreen in Storyline blocks and videos
If you use code blocks that need the microphone feel free to test that too.
If you run into an issue, it would be helpful if you could let me know (feel free to email me if you don't want to post it here):
- Your LMS and SCORM version (1.2 or 2004)
- Your course ID
- What didn't work
- Roughly when you downloaded that Connected Package
Thank you for helping us test!
ChristineT-gwx EliCahill ManalMP JamieDerry-a295 JenLynnRusso Kathyksigstadon EpicEdward
- JenLynnRussoCommunity Member
All worked for me: exit button, full-screen video (both MP4 and iframed YouTube), and full-screen Storyline! Our LMS is Docebo, and I used SCORM 2004.
- catganimStaff
JenLynnRusso thank you!
Related Content
- 8 months ago
- 2 months ago