Built to Connect

Integrations & Data Flow

Korus connects to your institution's systems through proven, low-overhead patterns. CSV over SFTP for enrollment data. SAML 2.0 SSO at launch. LMS LTI as our first post-launch priority. Nothing exotic to scope; nothing that puts your IT team on the critical path.

Integration status at a glance

IntegrationStatus
CSV/SFTP enrollment data ingestionAvailable at launch
SAML 2.0 SSOAvailable at launch
Transactional email (delivery webhooks, bounce detection)Available at launch
Data export to institutional data warehousesAvailable at launch
LMS LTI (Canvas)First post-launch priority
API documentationAvailable at implementation kickoff

Enrollment data — CSV over SFTP

Korus ingests enrollment data via CSV synchronization over SFTP. There is no requirement for direct SIS API access or a specific schema. Korus supports denormalized flat-file data (enrollment, course, and instructor data combined) or normalized relational data. Synchronization can be automated on a regular schedule or run ad-hoc as needed. Your institution's organizational structure — colleges, departments, programs — is derived from the enrollment data during onboarding and used for both survey scoping and permission management across all Korus products.

Why this matters: No SIS API project to scope. No vendor dependency on your IT team. Most institutions are productive on day one of data sync.

SAML 2.0 SSO

SAML 2.0 SSO is the authentication standard for Korus and is compatible with the identity providers higher education uses in practice. All access paths require SSO; there is no anonymous or unauthenticated access. Korus does not maintain its own student or faculty password database.

Why this matters: Required by procurement and security. Students and faculty sign in with the credentials they already have.

Transactional email

Korus sends automated student and faculty notifications through a reliable transactional email service with delivery monitoring and bounce handling. Send time is decoupled from survey open time — surveys can open at midnight while notifications go out at 9am.

Why this matters: Reliable delivery is a precondition for everything else. Delivery monitoring feeds the proactive failure alerts your administrators rely on.

Data export to your warehouse

Korus supports export of response and aggregate data to institutional data warehouses, with both CSV and PDF export available throughout the platform. BI-tool integration patterns are documented.

Why this matters: Your institutional research and analytics teams can incorporate Korus data into existing dashboards.

LMS LTI (Canvas) — coming soon

LTI integration placing Korus directly in the Canvas course navigation is the first post-launch development priority. This will give students one-click access to active surveys from the course they're already in, and give faculty in-LMS access to their Korus dashboard.

Why this matters: Student response rates rise when surveys live where students already are.

Got an integration question for your IT team?

Talk to us about your environment. We'll tell you straight whether Korus fits.