Skip to Main Content

Requesting an Integration in Blackboard

  • Blackboard Ultra

Last modified: December 10, 2025

This guide explains what to expect when requesting that a textbook, publisher tool, or other external resource be integrated into our Blackboard environment. Please note: this process does not include funding requests. Any associated costs must be handled at the department level. Some tools may be free to integrate.

UAS LTI Integration Approval Process Overview

This page outlines the process for faculty to request new integrations (LTIs) to be added to the UA Blackboard Learning Management System (LMS). Note: UAA and UAS share the same Blackboard implementation, managed centrally by UA.

LTIs are external applications that connect to Blackboard (or any LMS). Some are deeply integrated so users do not need to leave Blackboard or log-in again. You can think of them as plug-ins that extend what you can do with Blackboard. Commonly used examples include Textbook Integrations, VoiceThread, and Zoom.

The entire process of implementing a new integration typically takes 6-8 weeks from initial request to production deployment, assuming the vendor provides timely responses.

Step 1: Submit Software Review Request* to OIT (1-3 weeks)

*A Software Review Request is a formal request that applies to all new software, including LTIs, you can find details about requests to the UA Office of Information Technology (OIT) here.
  • For paid LTIs Faculty can work through their department administrator for any paid instructional or teaching tools. In these cases the department admin will submit a Software Review Request to UA OIT.
    Once the OIT Software Review Request is approved, the department admin should inform an Instructional Designer (ID), so that the ID can support the rest of this process. 
  • For free LTIs, faculty can work directly with an ID who will submit a Software Review Request to UA OIT on behalf of a faculty member or program and then support the rest of this process once the OIT Request is approved.

Step 2: Technical Configuration & Sandbox Testing (2-3 weeks)

Once OIT approves the software, an instructional designer will notify the UAS Blackboard admin to begin technical setup. This phase includes: 

  • The UAS Blackboard admin will confirm with all UA Blackboard Administrators that the tool meets our system requirements. 

  • The Blackboard admin, with the assistance of IDs, will review relevant technical documentation and API requirements. 

  • The UAS admin will configure the LTI in a Blackboard sandbox environment

  • IDs and faculty will need to assist the blackboard admin in testing the LTI in the sandbox environment to ensure it functions as expected. 

Note that initial testing confirms only that the integration gets to the initial landing page of the external service. Most integrations require additional login credentials by the faculty member to test the extended features. UAS does not provide funding for subscriptions to LTIs to IDs or admins.

 

Step 3: Production Deployment Estimated Time: (1-2 weeks)

Upon successful testing, the UAS System Admin will schedule full deployment during a maintenance window. At this time:

  • The LTI will be enabled in the production environment during the next maintenance window. 

  • Faculty will be notified of availability by an ID. 

  • Faculty can schedule a training session with an ID if desired.

Important notes

Remember to submit requests 6-8 weeks before you want an LTI in your course, requests submitted during peak periods (for example the start of semester) may experience delays, and the timeline depends partly on vendor cooperation with technical requirements.