New Version Published Notification
Overview
Program Equivalents and Versioning are now supported for content shared through Multisite.
Previously, these features could only be used for programs a firm owned outright, they had no effect on programs shared between a Publisher and Subscriber. With this update, firms in a Multisite relationship can decide who is responsible for defining equivalency relationships and creating new versions for shared content, and that decision determines how the two features behave for both sites.
As a reminder:
Publisher: Owns the content and shares it with another site.
Subscriber: Receives content created by another site.
Note: These settings apply per Publisher/Subscriber relationship and affect only content that is actively shared through Multisite. Programs that are not shared continue to follow the standard Equivalents and Versioning workflows described in their respective articles.
Key Concepts
Publisher Owns Program Equivalencies (setting): Determines whether the Publisher or the Subscriber is responsible for defining equivalency relationships involving shared content.
Publisher Owns Program Versioning (setting): Determines whether the Publisher or the Subscriber is responsible for creating new versions of shared content.
Enabled (Publisher Owns): The Publisher defines the relationship (equivalency or new version), and it cascades down to Subscriber automatically. Subscribers see the relationship but cannot create, edit, or remove it.
Disabled (Subscriber Controls): Each Subscriber is responsible for managing the relationship independently for their own site. Nothing the Publisher defines on their own site is shared down, and nothing a Subscriber defines is shared back up or to other Subscribers.
Multisite Set-Up
Two new toggles are available to Publisher sites, found in the same location as other Multisite configuration:
From the Administration menu, select Site Settings.
Expand the Multisite section at the bottom of the form.
Locate the two new toggles:
Publisher Owns Program Equivalencies
Publisher Owns Program Versioning
Enable a toggle if your firm wants to retain control over that feature for content you share. Leave it disabled if you'd like each Subscriber to manage that feature independently for your shared content.
Caution: Once a toggle has been enabled, it cannot be reverted through the Organization Settings UI. Decide on your ownership preference for each feature before turning it on, and reach out to your Customer Success contact if you believe your setting needs to change.
For Publishers
When You Own Equivalencies
You are the sole authority for defining equivalency relationships on programs you share. Set these up the same way described in the Program Equivalents article.
Once both programs in an equivalency relationship are shared to a given Subscriber, the equivalency (directionality, retroactivity, and credit-worthiness settings) is automatically shared to that Subscriber.
Note: If only one of the two programs in an equivalency has been shared, the relationship is not shared until the second program is also shared to that Subscriber.
Subscribers cannot create, edit, or delete equivalencies involving your shared content while you hold this setting.
When You Own Versioning
You are the sole authority for creating new versions of programs you share. Set these up the same way described in the Versioning article.
Once both the original program and its new version are shared to a given Subscriber, the version relationship is automatically shared to that Subscriber.
Subscribers cannot use Add Version or Link to a 3rd Party Program for your shared content while you hold this setting.
Important: Sharing a version does not automatically move a Subscriber's in-progress users to the new version. Your User Impact setting (Replace, Append, or Completed Equivalent) is shared as a suggestion, but each Subscriber administrator decides independently whether and when to apply it to their own learners. See New Version Published Notification below.
When You Relinquish Control (Setting Disabled)
You will not be able to create equivalencies or new versions for programs you've shared, this responsibility passes entirely to your Subscribers.
You may still define equivalencies or new versions for content on your own site, but those relationships will not be shared to Subscribers.
For Subscribers
When the Publisher Owns Equivalencies
You will see equivalency relationships the Publisher has shared to you reflected on the shared program's Equivalencies tab, just as with any other equivalency.
These relationships are read-only, you cannot edit, remove, or override them.
All standard user-facing behavior applies: Equivalent Complete badges, My Learning status, Dashboard widgets, and Learning Plan registration will reflect the Publisher's equivalency settings.
When the Publisher Owns Versioning
When the Publisher shares a new version of a program you've received, you'll be notified (see New Version Published Notification).
You retain full control over your own users: you decide whether to adopt the Publisher's suggested User Impact setting (Replace, Append, or Completed Equivalent) or manage the transition yourself.
You cannot create your own version of Publisher-owned shared content, or duplicate/author the underlying session, while this setting is in effect.
When You Control Equivalencies
You can create equivalency relationships between the Publisher's shared programs and your own locally-owned programs, following the same steps in the Program Equivalents article.
These relationships are scoped to your site only, the Publisher and any other Subscribers will not see them.
All standard behaviors (directionality, retroactivity, credit-worthiness, Equivalent Complete status) work exactly as they would for equivalencies between two locally-owned programs.
When You Control Versioning
You cannot use Add Version to create a new version from an existing program you don't own.
Instead, use Link to a 3rd Party Program from the Versioning workflow to connect a newer instance of the Publisher's content to the version your users have already engaged with. This is the same 3rd-party linking option described in the Versioning article.
You will not have the ability to author or duplicate the Publisher's original session content.
New Version Published Notification
When a Publisher who owns Versioning shares a new version, Subscribers can be notified so an administrator knows to review and act on it.
Set-Up
From the Notifications menu, select Event type: New Version Published.
Enter the Template Name, Email Subject, and Message.
Choose whether to send this notification automatically when a new version is shared to your site.
Define your Recipient list (comma-separated email addresses).
Filter by Publisher Site to control which Publisher's version releases trigger this notification.
Compose your Email Message using the available tags, including the new Multisite-specific tags:
User Impact Setting: the Publisher's suggested approach (Replace, Append, or Completed Equivalent).
User Impact Preview: a summary of how many of your users would be affected, broken down by those who would be enrolled/assigned versus those with a passed status that would be preserved.
Review Publisher Settings: a link directly to the "Review Publisher Suggested Impact" area of the new version, where you can opt in or out of the Publisher's suggested user impact.
Note: Opting in applies the Publisher's suggested User Impact setting to your in-progress users. Opting out leaves the transition entirely in your hands, you can manage affected users manually through Program Actions and Manage Attendees at your own pace.
Reporting
Existing Equivalencies and Versioning reports now include additional columns to reflect Multisite activity.
Program Equivalencies Report
Shared To (Publisher view): Comma-separated list of Subscriber sites the equivalency has been shared to.
Shared From (Subscriber view): The Publisher who shared the equivalency to you.
Version History Report
Shared To (Publisher view): Comma-separated list of Subscriber sites the version has been shared to.
Shared From (Subscriber view): The Publisher who shared the version to you.
-
On the Subscriber's report, additional columns reflect where you stand with a Publisher-shared version:
Version Created By: The Publisher's name.
Version User Impact Settings and Transition Timing: Show the Publisher's suggestion if you've opted in, "Manual Action" if you've opted out, or "Action Required" if you haven't yet made a choice.
New Version: # of Users Assigned / Enrolled: Reflects your affected user counts if opted in, or "Opt Out: Manual Action" if opted out.
Related to