CloudShare's Learning Management System (LMS) integration provides a seamless user experience for students, allowing them to access CloudShare's hands-on training environments directly from your LMS courses. Whether you use Learning Tools Interoperability (LTI) integration or CloudShares's API calls, this integration streamlines demo delivery and enhances your end users’ experience.

Integration Options

CloudShare offers a number of methods for integrating with your LMS:

1. Learning Tools Interoperability (LTI) Integration: This standard protocol provides a complete and seamless lab experience for LMS platforms that support LTI v1.1 and v1.3. Users can access CloudShare environments from within your LMS courses effortlessly.
2. CloudShare API Call: With CloudShare’s API, you can create a prepared URL to our public API and give your LMS users direct access to virtual labs. This method is suitable for LMS platforms that do not support LTI but can incorporate external URLs.

LTI Integration

CloudShare supports the Learning Tools Interoperability (LTI) specification, a cross-platform protocol that enables learning platforms (like your LMS) to securely communicate and share data with external platforms (like CloudShare). LTI facilitates key learning platform activities, such as single sign-on, role definition, contextual information sharing, secure data handling, real-time interactions, and more. The advantage of using LTI with your LMS is that it provides all this functionality without the need for custom program code or dedicated APIs.

By supporting LTI, CloudShare allows you to offer all of our advanced virtual lab features to your instructors and students directly from inside your LMS.

Limitations

Classes deleted in CloudShare will still appear in the LMS and must be manually deleted there and vice versa.

LTI Versions Supported

CloudShare supports LTI 1.1 and LTI 1.3

Note: LTI 1.3 is currently in Beta.

How CloudShare Works with LTI

When working with LTI, your LMS is referred to as the LTI Platform, and CloudShare is the LTI Tool. 

When launching a virtual lab, it is crucial to ensure that your LMS sends the launching user's name and email address to CloudShare through the LTI request. This allows for seamless user identification and authentication within the virtual environment.

When integrating CloudShare with an LMS, a CloudShare virtual lab cannot be hosted within an iFrame. To ensure optimal functionality, make sure the host browser is opened in full-screen mode. This ensures a smooth and uninterrupted user experience during sessions.

CloudShare maps the LTI variables to standard integration fields:

• Content URL: This is the URL of the CloudShare content (i.e., the class) that will be accessed from the LMS module. CloudSHare maps this to a field called LTI Launch URL.
• LTI Client Key: This is CloudShare’s unique LTI Toolaccount ID, allowing the LTI Platform(LMS) to identify CloudShare as the owner of the virtual lab. CloudShare maps this to a field called LTI Key.
• LTI Client Secret: This password authenticates CloudShare as the LTI Tool account. CloudShare maps this to a field called LTI Secret.

Creating an LTI Integration

To create an LTI integration for a virtual lab, click the class and the pencil icon near Connect with your LMS in the Access block.

This will open the LMS Integration Window. 

Select the desired LTI version:

None: 

Choose this option if you want to disable the LTI integration.

LTI 1.1: 

Copy and paste the three CloudShare keys from the dialog box into your LMS and click Apply.

LTI 1.3: 

This version requires mutual authentication, involving both CloudShare keys and LMS keys for enhanced security. 

1. Copy each authentication key from CloudShare and paste it into the corresponding field in your LMS course. 
2. Copy the relevant fields from your LMS to your CloudShare environment. Refer to your organization's LMS specifications or internal procedures to determine which LMS fields to use. Once the keys are added and authenticated
3. Click "Apply" to complete the integration.

Note: In both versions, you can connect multiple CloudShare classes to the same course; however, LTI 1.1 allows you to connect a class to one course on your LMS, while LTI 1.3 allows you to connect a class to multiple courses.

The CloudShare class will then be accessible from the LMS using the selected LTI version.

Once an LTI 1.3 integration has been completed, CloudShare classes will display the last accessed course and date for each class in the Access section.

Additionally, the LTI score report timer is set to update every minute. This frequent update interval ensures that learners' progress and performance data are always current, allowing for timely interventions and accurate tracking.

The most recent version of a class will appear in the LMS, reflecting any updates made in CloudShare.

Note: When a class is duplicated, the main instructor’s information will be copied as well, ensuring that all relevant instructor details are preserved in the new environment. 

Managing Classes and Templates

Once an class is connected, it serves as a template in the LMS. Adding more courses to the same class will create copies based on the initial template configuration. Connecting a class to a new course will create a duplicate of the class. Any changes made to the course will only be reflected in the copy of the class created for the course

Class-Level Integration With LTI 1.3

Overview

At the class level, having a subscription-based integration model means the integration process is streamlined and can be completed with the click of a button, allowing users to quickly share their CloudShare classes to the LMS without repeating the full integration process. Once the integration has been enabled, classes can be seamlessly shared with the LMS's Central Repository. This integration is crucial for efficient sharing and centralized management, making it essential for streamlined operations. By configuring the integration at the subscription level, every class under this subscription can be easily shared with the LMS's Central Repository, eliminating the need for repeated setups.

Note: The structure of classes in the Guided Journey, organized into sections, is shared through the integration with LTI 1.3. This ensures that the organized layout of the learning material is maintained across platforms, allowing for a cohesive user experience.

Integration Steps

Click the Class to open the Class Details page. Navigate to the Access tab of the Edit panel, which appears to the right of the Class Details page, and click the Share to LMS button.

This action will add the class to the LMS's Central Repository (CLOR), enabling you to connect the class to one or more courses. When the integration is successful, a notification will appear at the top of the page. 

Note: One class may be connected to multiple  courses. Connecting one class to multiple courses allows for the reuse of content without the need for creating a separate class for each course. Each course will access the same core class, but any changes made at the course level remain isolated, allowing customization without affecting other courses.

If this process fails, an error message will appear. 

Check the integration configuration to ensure you are not experiencing a failure to share to the LMS. If the issue persists, try sharing the data again to see if the problem resolves itself. Sharing to the LMS refers to sending or syncing information from CloudShare to the LMS, ensuring the integration is working correctly. 

Note: Integration configuration may only be checked by users with account manager permissions. 

Managing Classes shared with LTI 1.3 

Once an class is integrated with an LMS via LTI 1.3, it’s displayed in the LMS's Central Repository as learning material and can be linked to your  courses. When the class is shared, you will see the following indication:

Shared with the <course name> course, last accessed on <last launch time>

This shared class can be attached to one or multiple courses. When sharing more than one course, the same class that was initially shared with the LMS will function as an "class template." This "class template" is what appears in LMS's Central Repository, and based on its configuration, all other courses utilizing this learning material will have their own isolated copy, duplicated from the template.

There are two key identifiers with icons for this:

• Class  Template: When added to more than one course, it serves as a predefined setup or configuration that can be reused across multiple courses.
• Duplicated from the experience: When added to more than one course, CloudShare generates copies based on the original class template. Changes made to individual courses only affect the respective copy of the experience.

Note: The duplicated class will only be presented on the CloudShare side after the first LTI launch.

Accessing CloudShare via LMS

For Students

Students can launch CloudShare hands-on classes directly from their LMS course. The integration provides a seamless transition, eliminating the need to switch contexts.

LTI 1.1

When implementing an LTI 1.1 integration, if student information (first name, last name, email) is not shared by the LMS, access to CloudShare will be denied, and the student will see an error message prompting them to update their details in the LMS.

LTI 1.3

When using an LTI 1.3 integration, CloudShare requires email information to uniquely identify students; however, if only partial information is provided, CloudShare will generate an internal email to ensure unique identification.

For Instructors

LTI 1.1

Instructors will be forwarded directly to the CloudShare class.

LTI 1.3

Instructors can manage their CloudShare sessions directly from the LMS. When launching a CloudShare activity, they will be directed to the instructor console if they are already logged in to CloudShare.

If the instructor is not logged in, they will be prompted to authenticate. After successful authentication, they will be forwarded to the instructor console.

Instructors must be defined in the class with the same full name and email that are also configured in the LMS to enable authentication.

Managing Classes and Templates

Once a CloudShare class is connected, it serves as a template in your LTI. Adding more courses to the same class will create copies based on the initial template configuration. Any changes to the original class will reflect across all template copies in the LTI.