LTI request process

Learning Tools Interoperability (LTI) allows third-party educational tools to work within Canvas. These tools extend Canvas functionality and may exchange student data.
View the current list of approved tools: https://www.usu.edu/teach/help-topics/teaching-softwares/lti-tools/

New requirements for LTI integrations (Spring 2026)

Due to recent changes in legislation regarding student data privacy and institutional purchasing requirements, all LTI integration requests—regardless of cost—must go through the university’s formal purchasing process. This includes tools that are free to the university, paid by a department, or paid by students (for example, through course fees or access codes).

If there is no existing contract or agreement with the LTI vendor:

• The vendor must be onboarded as a university vendor.
• A formal contract must be established by the requesting department before the tool can be installed in Canvas.
• The contract (or an addendum) must include language that explicitly allows use of the tool with Canvas through the Learning Tools Interoperability (LTI) specification.

Before you request an LTI

Because student data may be sent to and received from an LTI, all LTI requests must be reviewed and approved.
Requests follow the standard USU procurement process and should be submitted by your department’s business office using the Document Approval form in ServiceNow.
Document Approval form: https://usu.service-now.com/aggies?id=sc_cat_item&sys_id=d9d87e6913d2bf009df150bf3244b0d2

The review typically evaluates:

• Privacy and student data handling
• Cost
• Data security
• Responsible use of AI (if applicable)
• Accessibility

Important: LTIs and publisher tools can’t be added to Canvas until the review is completed and approved.
Approval isn’t guaranteed for a specific term or academic year.

Typical timelines

• Reviews typically take 4–6 months (sometimes longer).

Approval outcomes

• If approved, the requester is notified.
• If not approved, the requester is notified of the reasons and alternatives may be suggested (when available).

If the tool you want isn’t already on the approved list, your business office should start the procurement process.

What to attach to the Document Approval request

Work with the vendor representative to collect and attach the following documents:

• Higher Education Community Vendor Assessment Toolkit (HECVAT)
• Accessibility policy
• Voluntary Product Accessibility Template (VPAT)
• Privacy policy
• Terms of service (what students must accept before using the tool)
• Any additional documents required during review (can be submitted after the initial request)

Most tools collect Personally Identifiable Student Data (PISD). If the tool does, you must complete the Governmental Entity, Data Processing, and Electronic and Information Technology Accessibility Addendum (GEDP) as part of the contract.
Your business office should have access to the GEDP document.

Configure approvals in the Document Approval form

In the approval section:

1. Set Does this document require approval from more than one individual? to Yes.
2. Set Do approvals need to be obtained in a specific order (sequence)? to Yes.
3. For How many levels are needed?, select 2 or more (typical).

Level 1 approvers

Add both of the following approvers under Level 1:

• Tyler Clair

  • Approving As: Other → Canvas Administrator
  • Function / Role: Approver

• Megan Cox

  • Approving As: Other → Digital Accessibility Officer
  • Function / Role: Approver

Remaining approval levels

Add the individuals in your department who are responsible for approving contracts.

Purchasing requirements (Document Approval form)

In the purchasing section:

• Set Does the contract/agreement need to be sent to Purchasing? to Yes.
• If the tool cost is covered by student fees, enter 0 for Annual cost and Total contract cost.
• If the tool is paid by other means (for example, a departmental P-card), your business office may need additional steps to assess costs.

Personally Identifiable Student Data (PISD) section

In the PISD section:

• Set Will the Contract Counterparty have access to or receive PISD as part of this contract? to Yes.
• Set Is the purpose of the contract to set up terms for student internships, experiential learning placements, or a study abroad program? to No.
• If there’s an existing contract, answer the question about whether it already includes terms that protect student information.
• If you answer No, follow the on-screen directions that appear below the question.

Questions

• Canvas integration and HECVAT: Tyler Clair (Canvas Administrator) — tyler.clair@usu.edu
• Accessibility policy and VPAT: Megan Cox (Digital Accessibility Officer) — accessibility@usu.edu
• PISD: Fran Hopkin (Registrar) — fran.hopkin@usu.edu
• Privacy policy and terms of service: Liliana Acosta (Data Privacy Officer) — liliana.acosta@usu.edu

Note: Teaching and Learning Technologies and the Center for Instructional Design & Innovation are not responsible for establishing contracts or procuring the tool. They can help clarify requirements, install the tool, and participate in the review process.