/
D2L Integration Procedure

D2L Integration Procedure

Overview 

In some cases it is possible to integrate third-party tools into D2L to give students and instructors a more seamless experience by sharing data including credentials, content links, rosters, and grades.  

The following procedures will be used to guide instructors through the process. 

Important: Integration requests must be submitted at least 90 days before the intended use date. 

Questions to Consider Before Requesting Integration

  1. Does CMU have something already in place to meet your needs? 

  2. Does the technology meet current accessibility standards? (WCAG 2.0/2.1, a current VPAT, etc.) 

  3. Have you provided enough lead time for tool integration? 

    1. Submit the request to acquire new software at least 90 days prior to intended use, some approvals may take longer.

  4. Are the students protected? 

    1. Does the tool collect or keep sensitive, protected, or FERPA regulated data? 

  5. Is there a cost for the tool? If so, how will it be funded? 

  6. Who is the contact person associated with the vendor? 

    1. Gather vendor information. 

  7. How will the vendor provide support for the tool? 

    1. Instructors are responsible for contacting the vendor directly for any issues or troubleshooting.   

  8. Will a contract be required with the vendor? 

Criteria for Integration

Third-party tools will be considered for LMS integration if they meet the following criteria: 

Course Scope and Use 

  • Must be used in courses with multiple sections, high enrollment, or recurring curriculum. 

  • Tools for one-time or low-enrollment courses are typically not approved for full LMS integration. External use (outside the LMS) may be considered for these cases. 

Student Impact 

  • Must enhance the student learning experience (e.g., engagement, assessment, content delivery). 

  • Preference given to tools that benefit multiple programs or departments. 

Technical and Compliance Review 

All tools must undergo a review process to ensure compliance with the following standards: 

  • Security & Privacy: Must comply with FERPA, CMU Data Protection Policy, and CMU Privacy Statement. 

  • Accessibility: Must meet WCAG 2.1 AA standards 

  • Contracts & Procurement: If an agreement needs to be signed, CMU contract manager must review all contracts prior to commitment. 

  • Functionality: Must work reliably within D2L and not disrupt workflows.  

Review & Approval Process 

To begin, submit a request to Acquire New Software.  

The approval process involves a thorough review (by IT, the Procurement and Payment Services Department, EAS, and the Center for Digital Learning and Innovation) to ensure that the product meets accessibility, functionality, security, and privacy standards.  

Only tools that pass all evaluations will be approved. If any requirement is not met, the tool will not be integrated into D2L.  

Support Limitations 

Instructors are responsible for contacting the vendor directly for any issues or troubleshooting.