Overview
Nectir AI integrates with Canvas using two methods: LTI 1.3 and the Canvas API. This page provides a summary of each integration method, the security and compliance standards Nectir follows, and what data is accessed, helping IT teams review and approve the integration.Integration Methods
Nectir offers two ways to connect with Canvas, each serving a different purpose. Institutions can use one or both depending on their needs.- LTI 1.3 Integration
- API Integration
The LTI integration embeds Nectir AI directly inside Canvas courses, providing a seamless experience for students and instructors.With LTI, Nectir can:
- Provide seamless single sign-on (SSO): Students and instructors access Nectir directly from Canvas without creating new credentials.
- Automatically enroll users in the correct Workspace and Group: Users are added to the Workspace and placed into the Group that corresponds to their Canvas course, with roles provisioned based on their Canvas permissions. See LMS Role Mapping for details.
- Deliver AI-powered support inside the LMS workflow: Learners receive 24/7, course-specific assistance without leaving Canvas.
LTI Setup Guide
Step-by-step guide to installing and configuring the LTI integration.
Who Can Set Up the Integration
Both integration methods require coordination between your Canvas administrator and a Nectir Workspace Owner or Editor.
- Canvas Admin access is required. Only users with administrative privileges in Canvas can create and configure LTI developer keys or API credentials.
- Nectir Workspace Owner or Editor access is required. A Nectir user with the appropriate role must complete the integration setup on the Nectir side.
Security and Compliance Standards
Nectir is built with enterprise-grade security and educational compliance in mind.SOC 2 Type II Compliance
SOC 2 Type II Compliance
Nectir maintains SOC 2 Type II compliance with verified controls for security, availability, and confidentiality. Our compliance is continuously monitored and audited.
FERPA Compliance
FERPA Compliance
Nectir is designed to help institutions meet their FERPA obligations. Student data is processed only as necessary to support authorized educational use cases, with data minimization and appropriate privacy protections in place. Nectir does not sell student data or use student data for advertising purposes.
Secure Authentication
Secure Authentication
The LTI integration uses LTI 1.3 with OAuth 2.0, ensuring encrypted, standards-based authentication without shared credentials. The API integration uses scoped OAuth 2.0 tokens with read-only access configured by your institution.
What Data Nectir Accesses
Nectir limits data access to what’s required to support authentication and course-level features. The data shared with Nectir depends on the integration method used.- LTI Data Access
- API Data Access
When Nectir is launched from Canvas using LTI, the following information is provided as part of the standard LTI launch process:
This data is limited to the course context from which Nectir is accessed.
| Data | Purpose |
|---|---|
| Name | User identification and display |
| Email address | Authentication and communication |
| LMS role | Determines Workspace and Group permissions via role mapping |
| Course information | Course IDs, names, and section identifiers |
| LMS user ID | Account mapping and linking to Canvas identity |
Data Nectir does not access through LTI:
- Grades or gradebook data
- Assignment submissions
- Canvas administrative settings
- Data outside of the launched course context
Trust Center
For full details on Nectir’s security practices, audit reports, and compliance documentation, visit the Nectir Trust Center.Visit the Nectir Trust Center
Access up-to-date security reports and compliance evidence commonly requested during IT security reviews.