Topics Map > Canvas

Canvas - Enabled Application Configurations [UW-Madison]

This document lists the integrations currently enabled in UW-Madison's version of Canvas.

Learn@UW-Madison actively supports the integration of third-party applications and publisher Digital Learning Tools (DLT) with Canvas. Support of the integration does not imply that use of the application is supported by the Learn@UW-Madison service, unless explicitly stated. In most cases, support and maintenance of the application or DLT is between the user(s) and third-party vendor. Additionally, Learn@UW-Madison cannot support integrations not listed here. If your integration is not listed, review the External LMS Integrations process, and submit a request if interested via the request form.

Note: Canvas includes a link to EduAppCenter within the Apps tab of your course settings. However, the apps listed there are not necessarily approved for use at UW-Madison. Please refer to the list below for approved applications.

Integrated Applications Available for Use

The following applications are integrated with Canvas and can be used by faculty.
Canvas External Integrated Applications

External Integrated Application


Who provides support?

Atomic Assessments Atomic Assessments - Overview [UW-Madison]  Learn@UW-Madison
Box Vendor
Canvas Chat Learn@UW-Madison
Canvas Commons Canvas - Getting Started with Canvas Commons [UW-Madison] Learn@UW-Madison
CENGAGE Learning

Includes applications like MindTap.

Cengage Support

Course Summary Canvas - Using the Course Summary Tool [UW-Madison]  Learn@UW-Madison
Engage eText

Engage - Engage Overview [UW-Madison] 

DoIT Help Desk and Learn@UW-Madison
Kaltura Canvas - Options to Upload and Share Video in Canvas with Kaltura MediaSpace [UW-Madison] Learn@UW-Madison
Macmillan Learning Includes applications like Achieve. Vendor 
Microsoft Office 365 (One Drive) Learn@UW-Madison
Course Syllabus (HelioCampus AC) HelioCampus AC - Syllabus - Using the HelioCampus AC Syllabus Tool [UW-Madison]  Learn@UW-Madison
Pearson Includes applications like Pearson "MyLab and Mastering" and "Revel"
Pearson Apps installed via AppCenter

MyLab and Mastering Support
Revel Student Support
Revel Instructor Support

Piazza Piazza - Create a Piazza Account [UW-Madison] Vendor: Piazza, How to get help
SCORM Canvas - About the SCORM tool in Canvas [UW-Madison] Learn@UW-Madison
Attendance (Roll Call) Learn@UW-Madison
Top Hat Top Hat - Syncing Grades and Rosters with Canvas (LTI 1.3) [UW-Madison]  Vendor: Top Hat Success Center or (888) 663-5491
TurnItIn Turnitin - Using Turnitin with Canvas [UW-Madison]  Learn@UW-Madison
Sift & Winnow: Libraries Module TBD Learn@UW-Madison / Libraries
Vimeo Vendor
W. W. Norton & Company Vendor
YouTube Learn@UW-Madison
Zoom Web Conferencing (Zoom) DoIT Help Desk and Zoom team

Canvas App Center & Adding Additional Applications

All Canvas courses contain the App Center, which allows instructors to install whitelisted LTI apps in their course. Users can follow the "How do I add an External App in my course?" guide.

The Canvas App Center defines the following levels of privacy:
  • Anonymous: No identifying information about the user will be sent to the vendor.
  • Email Only: The user's email is the only identifying information sent to the vendor.
  • Name Only: The user's name is the only identifying information sent to the vendor.
  • Public: Various identifying information (name, email, Canvas ID, SIS ID of the course, SIS ID of user, etc.) is sent to the vendor.

Source: How do I manually configure an external app for an account?

Approval Process Based On Levels of Risk

The level of risk associated with various LMS integrations varies depending on two factors:

  1. They type of data transmitted from the LMS to the integrated application
  2. The technology used to integrate the application into the LMS

We define four levels of risk based on these factors:

Level 1 - Anonymous - External LMS Integrations
Those apps in the App Center which are listed as “anonymous” will be whitelisted by default. Other integrations determined to be “anonymous” by LMS developers and administrators may also be whitelisted.

Level 2 - Non Anonymous - External LMS Integrations
First, it's important to keep in mind that student, faculty, and course data can be put at risk if shared with non-UW-Madison entities, such as third-party vendors. Therefore, the UW-Madison CIO's Office requires that all integrations meet  guidelines for privacy, intellectual property, security and records retention.  Interested users should review the the following KB  External LMS Integrations and submit a request if interested via the request form. Learn@UW personnel will ensure that appropriate legal agreements are in place before allowing non-anonymous apps to be integrated with our LMSs. To the extent possible, given time and resource limitations, Learn@UW personnel will assist faculty in obtaining these legal agreements through normal purchasing channels.

Level 3 - Local LTI-Based LMS Integrations
Locally written and supported integrations using LTI will in most cases be approved by default. This is because the data sharing will be between a supported LMS and other services for which UW-Madison has ultimate responsibility. However, depending on circumstances,there may be some concern for the security and professional operation of the other services. Services developed and maintained by recognized UW development groups such are DoIT AT or the UW-Madison Moodle service will be accepted by default. Approval of services provided by other development groups may need vetting by OCIS.

Level 4 - Non LTI-Based Integrations
Non LTI-based integrations are ones that involve injecting third-party code into the LMSs code base, e.g. Moodle plug-ins, or utilize an API with a high-level access key. This includes integrations that utilize LTI for part of their functionality, but other integration techniques for other parts of their functionality. For example some external integrations utilize LTI for single sign-on purposes, but code injection for gradebook sync. Since access to the LMSs gradebook is a very sensitive matter, these integrations will require close scrutiny LMS developers and managers or OCIS, as appropriate to the specifics of the situation.

Canvas Course Navigation & Integrated Applications

All Canvas courses have a standard ("default") Course Navigation menu when they are first created.

In order to keep the Canvas default Course Navigation a manageable size, integrated applications are not generally added to the default Course Navigation. The Learn@UW Madison team uses the following standards to judiciously populate the default Course Navigation:

  1. The default Course Navigation contains core Canvas tools (such as Discussion, Grades, Syllabus, and so on). It also contains tools which offer no technical option for removal from the default Course Navigation, such as Google Drive. 
  2. General practice for integrating third-party applications with Canvas does not include adding the application to the default Course Navigation. Instead, such applications will be available for instructors to add to the Course Navigation on a course-by-course basis.

Keywordscanvas external apps lti application configuration app center LMS whitelist whitelisting cengage mindtap pearson mylab and mastering publisher digital learning tool tools revel dlt integration vendor piazza collaborate box chat atomic assessments kaltura syllabus AEFIS commons canvas roll call pearson turnitin vimeo top hat youtube norton lti inventory sheet   Doc ID65466
OwnerLearn@UW MadisonGroupLearn@UW-Madison
Created2016-07-26 14:31:00Updated2024-02-20 14:37:26
SitesDoIT Help Desk, Learn@UW-Madison
Feedback  0   0