Enhance content collaboration and efficiency between two or more of your Learning lifecycle platforms with the Add-on Multi-Tenant feature. Seamlessly share modules across connected platforms, fostering a more interconnected and streamlined experience.
🧠This article is relevant for you who:
Has more than one Learning Lifecycle Platform
Are you considering expanding with a second or more Learning Lifecycle platform(s)*
*Are you curious as to why you could expand with an extra platform: read more here
The Multi-Tenant feature enables a platform to establish a relationship with one or multiple platforms, allowing the sharing of modules between them. Whether you're working on a joint project, sharing resources, or ensuring consistency across your organisations, Multi-Tenant empowers Administrators to extend the reach of their modules beyond a single platform.
How to get started
Establishing Connections:
Reach out to your Customer Success Manager or [email protected]
Upon agreement, Learningbank will add the feature to your account and activate it on your platform
Select Modules:
Go to your module overview & choose the module you want to share from the platform.
Select the connected platforms where you want the module to be accessible.
Add Company platform
Select and add the platform you wish to share the module with
OBS: if the you seek platform does not appear in selection list, reach out our support to get it added
Access Permissions:
Decide the level of control for each shared module:
Can View (View Only): the platform can see and utilise the module but cannot make any edits.
Can Edit: Allow the platform to modify the module. the changes will update the module across all connected platforms and the sharing platform.
Allow duplicate: Allow the platform to duplicate the module, making it possible to add unique changes to the deplicated module locally, without sharing it across platform or updating the core module
Best practice🌟
Core content platform: Consider deciding on one platform being your core content platform. This will be where all shared/global content should be created. This approach will aid you in keeping a clearer overview of where the original content was created and who owns it.
Edit permission: Be critical of granting Edit permission on your shared module. Is the purpose of the shared module to maintain consistency? Do you want to ensure the original version is not overwritten? Then do not apply edit rights. Instead, if a platform needs to add unique edits to the content, they can choose to copy/duplicate the module, creating a new module as a local version. This new local version will have no connection to the shared module.