Blackboard Integration Policy

Policies Regarding the Building Blocks, Extensions or Add-Ons that May Be Integrated or Otherwise Interact with the LMS

Terms and Descriptions

  • The designated university learning management system (LMS) at the University of Louisville currently is Blackboard (Bb).
  • Building blocks, or blocks, are small applications integrated into the Blackboard LMS that extend the usability and functionality of Blackboard, aid in the administration of Blackboard, or otherwise provide customization. Blocks installed into Bb range from providing simple links to outside systems to sharing student data or adding additional course tools.
  • LTI, Learning Tools Interoperability, is an integration that can be used with an LMS to connect with external service tools.
  • Integration refers to the process of and result of embedding third-party applications into Blackboard.
  • Any third-party application that has an interaction with Blackboard will be noted as an “integration” in this document even though the manifestation can take many forms.

Rationale for the Process of Approving Blackboard Integrations

The rationale for creating a policy regarding Blackboard integrations will consider system security, student data integrity, pedagogical implications, Blackboard performance and overall university compliance. Please note that a request for “your” integration to be placed into the LMS affects the entire system, all courses.

Process for Implementing Blackboard Integrations

In the past Learning Management Systems (LMS) support has been contacted directly by building block or integration vendors and/or individual faculty about installing integrations. A policy is needed to help structure the management of the increased amount of integration requests. In order to meet the most critical needs of the university, LMS support has developed a procedure. It will provide a consistent and timely response to all requests.

  1. All Blackboard integration requests require a request form to be filled out in total by the instructor or user intending to use the integration. Here are some considerations for the requestor. The requestor will be the primary contact for the integration process and as such will need to set aside time to work with the Delphi Center for Teaching and Learning, Information Technology, the vendor and any other university department, or entity, that may be affected or needed for the integration. The requestor will be the primary tester and will have to perform testing in the “testing” environment and user testing in the “user” environment. Please note the requestor may be required to interact directly with the vendor throughout the testing process.
    • Realize that a request and implementation if approved can take one to three months and even longer.
    • Keep in mind the initial start date required for your integration. The adoption date will be at a minimum in the semester proceeding the first intended use of the integration.
    • By submitting the request, the requestor agrees to be the point of contact for the implementation process.
    • By submitting the request, the requestor agrees to be the primary tester or designated tester.
    • The request form requires such information as the contact information for the third-party vendor in addition to the institutional benefit, costs involved and estimate of how many instructors or users would be using the integration.
    • The integration will be analyzed in many ways including its compatibility and impact on the system.
    • After the request is received the Delphi Center will notify the requestor within five working days as to the status of the request.
    • The requestor will be involved throughout the evaluation process so please ensure you or your tester have time for testing, analysis and consultation with the Delphi Center for Teaching and Learning, vendor or developer as needed.
      • Please note that each integration is unique and circumstances of which can affect the timelines for testing and implementation.
    • The evaluation process may include but is not limited to the following: IT policies, University of Louisville policies, FERPA guidelines, financial considerations, user surveys, Blackboard Advisory Committee review, Delphi Center Advisory Committee review, Delphi Center director’s approval, comparable higher education adoption and compatibility testing.
    • After the evaluation process the requestor will be notified.
      • If approved the requestor will be notified of the implementation date. The implementation of the integration in the production environment will follow the testing procedure of being tested in the testing and subsequently staging environments first.
      • Implementation date may also be affected by university and Information Technology schedules.
      • If not approved the requestor will be notified with the reasons of non-committal.


    1. LMS support will attempt to assist with integration functionality issues when appropriate, however support may be limited to and provided by the vendor/developer only.
    2. Priority will be given to existing Blackboard blocks, LTIs and other integrations.
    3. If an upgrade or patch to the Blackboard system renders an integration inoperable, it is the responsibility of the vendor to provide the Delphi Center with an updated version or specific fix for that integration. Blackboard upgrades will always take precedence over integrations and as such could render some integrations inoperable for some time after an upgrade or until a fix is provided.
    4. The Delphi Center maintains the right to disable or remove an integration or building block if a security vulnerability or any other university or system issue arises after it has been deployed in the production environment.
    ^ Top of Page