Canvas Features and Canvas Integrations

Features are delivered options from Canvas that can be toggled on and off. Feature requests are reviewed every two weeks by Canvas Course Designers and Power Users. More information on Canvas Features can be found in the Canvas Feature Options Summary.

Canvas integrations are applications hosted by third-party publishers which can be deployed within Canvas. More information on integrations can be found in the Canvas guide What are external Apps (LTI Tools)? 

Feature Requests:

Requesting a New Feature in Canvas

Click here to submit a feature request to Academic Outreach and Innovation (AOI).

Integration Requests:

For the sake of clarity in this document, the terms vendor and publisher are interchangeable and refer to the third party entity hosting the integration or service.

Review Existing Integrations in Canvas

Instructors and departments are encouraged to review the list of existing Canvas integrations to determine if a suitable or equivalent solution is already available in Canvas.

A list of current Canvas integrations can be found here. 

Integrations are customized solutions that can meet a variety of different needs, and generally fall in one of the following categories, although there may be outliers which may be classified as "Other":

  • Peer Review & Social Learning
  • Administrative & Content Management
  • Accessibility & Annotation Tools
  • Collaboration & Communication
  • Analytics & Student Success Tracking
  • Media, Video, & Interactive Content
  • Publisher Content & Courseware Integration

Considering these classifications when reviewing existing integrations may reveal that a suitable integration is already available in Canvas.

Requesting a New Integration for Canvas

Please be aware that all integration requests are subject to review and must meet requirements before they are granted. 

It is advised to not enter into a purchasing contract or agreement with the integration publisher until it has been approved. Unless all WSU reviews are approved, an integration will not be allowed to proceed.

Instructors and departments can submit their integration request using the Canvas Integration Request.

Deadline for Integration Requests

Please Note: Beginning September 15, 2026, deadlines for integration requests will be enforced. 
  • Requests to be implemented by Fall: Due March 15 of the same calendar year (e.g., Fall 2027 requests are due March 15, 2027)
  • Requests to be implemented by Spring or Summer: Due September 15 of the previous calendar year (e.g., Spring 2027 requests are due September 15, 2026)

Requirements for Integration

For an integration to be enabled in Canvas, it must first be reviewed for the following key criteria:

  • Suitability 
    • Is this integration the best choice to meet the needs of the instructor and their students?
    • Does this integration align with the goals and objectives of the requesting department?
    • Is there a substantially similar integration already available that meets the same need?
  • Security
    • Most integrations consume student data in order to deliver a service. Does this integration meet essential data governance requirements so as to not escalate risk where FERPA data is involved?
  • Accessibility
    • Title II guidelines define the Accessibility requirement standards, which WSU in turn strives to meet so as to afford the best learning experience to all students. Does this integration meet these standards?
  • Functionality
    • All integrations require testing to validate expected functionality and features. When this integration is deployed in a test environment, does it deliver its promoted functionality?
  • Leadership Approval
    • Integrations require approval at different stages of the onboarding process. Once evaluation steps have been completed, integration requests will be submitted to the Change Control Board for final approval before being enabled in Canvas.

Workflow for Integration Requests

Preparing for your Request
Vendor/Publisher Information and Documentation

Please be sure to gather any vendor contact information and pertinent documentation you may have, including a link to the product website. 

If you are in direct communication with a vendor or publisher, you can request the following documentation and forward it when you submit your request. 

This is industry standard documentation for integrations and is generally available upon request. If you are unable to procure the documentation, it will be requested in the review process.

  • Security - HECVAT, FERPA Policy, Privacy Policy, associated links
  • Accessibility - VPAT, associated links
  • Technical - Integration Setup and Use Documentation
Submitting the Request for Review

Instructors and departments can submit their integration request using the Canvas Integration Request form.

Review Process

Once an integration request is received, reviews will be initiated in the following sequence: Suitability, Accessibility, Security, Functionality, Board Approval.

If an integration fails to pass any step in the sequence, it will not move forward.

Suitability Review 

If a requested integration is not deemed suitable by Learning Innovations leadership for any reason, the requestor will be informed of the decision and will be advised to meet with the Learning Innovations team to discuss the rationale and to review alternative solutions that may already be available in Canvas. 

Security Review

Data management, privacy policies, and adherence to FERPA guidelines will be evaluated by the IS team. Supporting documentation may be requested from the vendor. 

  • If a requested integration is rated as a High Risk, it will not proceed.
  • If a requested integration is rated as a Moderate Risk, department leadership will need to acknowledge they have reviewed the knowledge base article Moderate Risk and Canvas Integrations.
  • If a requested integration is rated as a Low/No Risk, it may proceed without further approval or discussion.
Accessibility Review

If a requested integration is not deemed to meet accessibility standards, please review the accessibility coordinator's notes for rationale and guidance. 

Functional Review

Integrations will be configured in a test environment to ensure expected functionality is delivered. 

If an integration does not function in the WSU Canvas environment due to a product issue or a limitation of the configuration of WSU Canvas environment, the ES team will work with the vendor to resolve technical issues and ensure functionality. 

If functionality cannot be validated, a report of the limiting issue will be shared with the requestor and the vendor.

Leadership Approval

Once the Suitability, Accessibility, Security, and Functionality reviews have completed with success, the integration request will be scheduled with the Change Control Board for their next weekly meeting. 

With CCB approval, integrations will be deployed to WSU Canvas on a determined date.

Integration Request Considerations:

Timing of Integration Requests

Please bear in mind the deadlines for submitting integration requests. 

  • Integration requests are processed expediently, however, the timing of the request is an important consideration. Integration review engages members from different areas and it takes time for all review steps to be completed. 
  • There is a general moratorium in place on implementing system changes in the week leading up to the beginning of a semester, and in the two weeks following. This pause is in consideration of and to prioritize the increased load of registration and financial aid activities. 

AI Policies

Requested integrations should comply with departmental AI usage policies, and students must be informed if AI-assisted grading is in use.

AI‑assisted grading is currently one of the most frequent concerns reported to both the Provost’s Office and the Dean of Students. Using AI-assisted tools may expose the course—and you as the instructor—to issues that could progress through the Academic Regulation process AR 104 or beyond, particularly if your course does not include an AI policy that clearly permits students to use AI tools in their own work.

Workflow Overview for Canvas Integration Requests

The estimated timeline to review a new integration in Canvas is subject to the processes and workload constraints of each participant. 

  • Vendor Information Coordination. 
    • Documentation on the Integration is requested
      • Security - HECVAT, FERPA Policy, Privacy Policy, associated links
      • Accessibility - VPAT, associated links
      • Technical - Integration Setup, Administration, and Use Documentation

  • Suitability Assessment. 
    • Conducted by the Learning Innovations team with Academic Outreach and Innovation (AOI) to ensure the integration aligns with the pedagogical objectives of the university.
    • Should it be determined that the integration is not suitable for use in Canvas or otherwise conflicts with an existing integration, a representative from the AOI team will reach out to explore alternatives. 

  • Security Team Review of Integration. 
    • The IS security team will review integration documentation. Depending on specifics of the integration, further documentation may be requested.
    • In some cases, a contract may be requested of the vendor that includes WSU Data Security and Privacy language.
    • If an NDA or other agreement is required to release documentation, it is the requesting department/business unit's responsibility to manage and resolve that agreement.

  • Accessibility Assessment. 
    • The Accessibility Coordinator with Academic Outreach and Innovation (AOI) will ensure the integration aligns with the accessibility standards of Washington State University.
    • Should it be determined that the integration does not meet accessibility standards, or that accommodations must be made for use of the integration, notes from the Accessibility Review will be shared with the department's leadership for consideration. The report includes detailed findings, risk levels, and recommended actions related to the product’s use and potential Canvas integration.
  • Functional Testing in the test environment. 
    • This step is necessary to confirm expected functionality of the integration and assure that there are no conflicts with our systems.
    • The Canvas Test environment resets on the third Saturday of the month. Requests received in the week leading up that date might not be tested until after the third Saturday reset, as it will allow our team time to fully test the integration without interruption.

  • Change Control Board (CCB) Review and Approval. 
    • Integration requests are submitted to CCB after the Suitability, Accessibility, Security, and Functionality reviews have been completed with success.
    • CCB meets on Tuesday afternoons. Change requests must be complete and submitted by noon on the prior day.

  • Integration into Canvas. 
    • Many integrations can be added to Canvas the day after CCB approval.
    • Some integrations require the exchange of security key values with the integration publisher, which can occasionally span 1-2 business days.

Request more information on Canvas Integrations

For more information on Canvas Integrations or to address a specific concern, please reach out to aoi.support@wsu.edu.