2 July 2026

Connected Packages in Rise 360

Edit the course. Export it. Download it. Re-upload it. Test it. Repeat for every single change.
For teams managing more than a handful of courses, that cycle turns small edits into hours of admin — and it has been the standard LMS workflow for years.

The new Articulate 360 LABS feature, Connected Packages, lets Rise 360 authors upload an LMS package once, then push future updates straight from Rise 360 — reducing the need to re-export and re-upload SCORM packages for every update.

For Australian and New Zealand organisations managing compliance training, onboarding, product knowledge, customer service or sales enablement content, this could be a practical way to reduce LMS administration and keep learning content current.

How Connected Packages Works

Connected Packages creates a connection between your Rise 360 course and the LMS package learners access.

In simple terms:

Authors can also notify learners when content changes. When this option is enabled, learners will see an update banner the next time they refresh or log in to the training.

Currently, Connected Packages is available for Rise 360 only and supports SCORM 1.2 and SCORM 2004 exports. You can learn more from Articulate’s E-Learning Heroes article, Say Goodbye to Re-Uploads: Update Your LMS Content Directly from Rise 360 with Connected Packages, and the LABS discussion, New in LABS: Connected Packages.

Watch Articulate’s Connected Packages Demo 

Watch Articulate’s demo below to see how a Connected Package is created in Rise 360, uploaded to an LMS, and updated without repeating the full SCORM re-upload process.

Why This Matters for LMS Teams

Keeping learning content accurate is often harder than creating it — especially for compliance training, onboarding, product knowledge, sales enablement and large course libraries across Australia and New Zealand.

Every content change can involve instructional designers, LMS administrators, HR and compliance teams just to push one update live.

Connected Packages can help teams:

This is especially useful for courses that change often, such as compliance training, onboarding modules, product knowledge, sales enablement resources or customer service process updates.

Where Connected Packages Can Help Australian and New Zealand Teams

Many organisations across Australia and New Zealand manage training across multiple locations, departments, regions and business units. For these teams, keeping LMS content consistent and up to date can be a challenge.

Connected Packages may be useful for:

For example, if a policy changes or a product feature is updated, the learning team can update the Rise 360 course and apply the change without manually re-uploading a new SCORM package each time.

For local teams already using Articulate 360 through MicroWay, Connected Packages is another example of how Articulate continues to improve course creation, maintenance and delivery workflows.

Organisations building sales training can also explore MicroWay’s sales training solutions to see how Articulate 360 can support scalable enablement programs.

Before You Use It: Articulate LABS Status and What to Check

Connected Packages is currently part of Articulate LABS, which gives Articulate 360 customers early access to features that are still in development.

Because LABS features may change before full production release, teams should test Connected Packages carefully before using it in critical training environments.

Before using it widely, teams should check:

Because Connected Package content is hosted on Articulate systems, Australian and New Zealand organisations with internal data, procurement or compliance requirements should review this as part of their normal software governance process. Teams should also consider internet availability, internal IT review and data governance requirements before using it for critical training.

You can read more about the LABS program in Articulate’s blog post, Articulate LABS: A first look at what’s coming next in Articulate 360.

Connected Packages vs Traditional SCORM Re-Upload

Area	Traditional LMS Package Update	Connected Packages
Course update process	Export and upload each time	Edit and update from Rise 360
LMS upload	Repeated uploads	Upload once, then update
Best for	Rarely updated courses	Frequently updated courses
Supported content	Standard LMS packages	Rise 360, SCORM 1.2 and SCORM 2004
Status	Standard publishing workflow	LABS feature

Is Connected Packages Right for Your Team?

Connected Packages may be a strong fit if your organisation:

• Uses Rise 360 to build LMS courses
• Updates training content regularly
• Manages a large course library
• Wants to reduce LMS administration
• Needs a more efficient way to maintain compliance, onboarding or product content
• Has distributed teams across Australia and New Zealand
• Wants to keep LMS delivery while reducing re-upload work

It may be less relevant if your organisation rarely updates LMS content, only uses one-off courses, relies mainly on Storyline 360, requires strict LMS version history, or does not currently publish Rise 360 content to an LMS.

For critical or compliance-heavy training, it is best to start with a pilot course, confirm LMS behaviour and review any internal governance requirements before wider use.