Request for Integrations with Canvas or to Adopt New Tools
UCSB has a significant educational technology ecosystem. Canvas, the campus learning management system (LMS) is the hub for most of these tools. If you are looking for a specific capability to use as part of your courses or trying to integrate a third-party tool with Canvas, please review the current catalog of tools.
If there is not an existing tool or integration you may submit a request with information about the tool or platform using this form. The request will be transmitted to Instructional Consultants in Instructional Development, who will contact you for any additional information required.
Current Catalog of UCSB Tools
Tool or Integration Adoption Workflow
Click on the image to enlarge it
The process consists of five steps starting with an initial faculty request for a new tool and the final step ends with the adoption and deployment of the tool. Note, this process can take up to a year depending on the procurement timeline.
Step 1 - Faculty Discovery
The process begins with a faculty member identifying an instructional need and reviewing the library of available educational technology tools posted on the Educational Technology Inventory website. If an existing tool already provides the functionality the faculty member wants to use, the faculty member is directed to instructions on including the tool in their course site and appropriate training resources. If the functionality is unavailable, faculty are directed to complete an online intake form referred to the Instructional Consultants in the Office of Teaching and Learning. This form asks for information on terms and conditions, price, and procurement requirements. Form submission will lead to a consultation to clarify the desired outcome and discuss possible tool options. Based on the original Intake Form and with faculty consultation, an Instructional Consultant in the Office of Teaching and Learning brings the request to the LMS Steering Committee for consideration for adoption.
Step 2 - Steering Committee Review
The LMS Steering Committee considers the request during a regularly scheduled meeting. They may ask for additional information from the faculty member, Instructional Development, or Collaborate staff. The Committee may recommend the adoption or decline the request.
- If the Committee recommends adoption and the tool requires funding, a potential funding source is discussed.
- If the Committee recommends adoption and no funding is required, it may proceed directly to the procurement phase.
Step 3 - Determination of Funding Source (For Tools that Require Funding)
Based on the Steering Committee discussion, the funding source is either identified or the funding source is approached. The ITC, the CIO’s Office, the EVC’s office, the Collaborate Advisory Committee, academic departments, or other entities may be possible funding sources. Once a funding source has been identified, they proceed to the procurement phase.
Step 4 - Final Approval and Procurement
Collaborate will initiate procurement with Business and Financial Services (BFS). This may require vendor agreement to the terms of Appendix DS and possible proof of insurance. The Office of the Campus Information Security Officer (CISO) will also evaluate the tool for privacy and security issues. After the contract has been executed, the tool may proceed to technical adoption and integration.
Step 5 - Integration and Deployment
Collaborate will work with the vendor to enable integration with the LMS and conduct any necessary testing before full deployment. During this phase, the scope of training and documentation will be evaluated and, if necessary, be created.