...
| Info |
|---|
Be sure to plan Ahead! Integrations need to be requested during at least the semester prior to using the integration. For example, integrations wanted for Fall semester should be requested by early-mid Summer term. |
Action Items
...
(Responsibility of the requestor)
| 2. Fill out the SARB Security Review Form |
Request Timeline
Initial request for Integration, using the Integration Request Form – 5 business days
Information gathering phase
Need will be assessed, alternative (already existing) integrations may be suggested
A key consideration for new global integrations is the expected usage of the tool; new global integrations will not be approved if only a few courses use the tool
Security and Functionality Review – 15 business days
In the interest of protecting student data in compliance with University Policy 8060, the Office of Information Technology may review data storage, retention, and transmission, and deletion processes for third-party applications
To ensure interoperability with our campus technology ecosystem, the Office of Information Technology may perform a software architecture review of third-party applications
Testing – 15 business days
Integrations are run through one Canvas environment – our Canvas Test Development site.
Basic functionality of the tool is tested, as well as its interactions with other parts of Canvas
Contract Review – 30 business days
This step may be optional/skipped for free services or those already under contract.
Integrations requiring a contract will need to meet standards set by University Policy 6030.
SARB approval will be required for LTI integrations that have not gone through the SARB process. The following link contains the Software Application Inventory of LTIs that have been approved.
Integration – 5-10 business days
LTS staff will need to meet with a technical rep from the product company in order to install the integration.
...