Integrations
QFlowLearn connects to the systems institutions already use.
Admins need to see exactly how assessment content, rosters, launches, scores, grade return, and reporting move between systems. QFlowLearn makes those connections explicit so implementation teams know what is supported, what data moves, and where each security boundary sits.
Integration matrix
Each integration is described in plain operational terms.
| Area | RFP requirement | QFlowLearn response | Status |
|---|---|---|---|
| LMS launch | LTI 1.3 launch from course, assignment, or assessment context | OIDC login and signed LTI 1.3 launch resolve tenant, assessment, learner, role, service context, and delivery policy before runtime bootstrap. | Ready |
| LTI Advantage | Roster, assignment, and result return workflows | Dynamic Registration, Deep Linking content-item responses, AGS score passback, AGS line item access, and NRPS membership reads are implemented. | Ready |
| LTI Deep Linking | Let instructors select and place assessment links in the LMS | Deep Linking launch and signed content-item response endpoints are implemented. A polished LMS content-picker UI is the remaining packaging work. | Ready |
| Canvas and Moodle | Common LMS launch and gradebook flows | Use the LTI 1.3 and Advantage implementation as the standard integration path, then validate launch, roster, and gradebook behavior in each buyer LMS. | In build for launch |
| SIS and rostering | Import learners, sections, courses, schools, terms, and enrollment metadata | CSV and OneRoster CSV provisioning support preview, apply, learner and section membership import, orgs, academic sessions, courses, class metadata, idempotency, and run reports. | Ready |
| SSO | Institutional authentication and role mapping | Keep authoring, instructor, and delivery host boundaries explicit while mapping institutional roles to QFlowLearn permissions. | Planned |
| Content exchange | Move assessment content between systems | Import QTI 1.2, QTI 2.1/2.2, QTI 3.0, IMSCC, Moodle XML, GIFT, and Aiken. Export clean QTI 3 packages. | Ready |
| Results export | Export results for SIS, warehouse, and accountability reporting | Provide learner-level, aggregate, standards-level, item-level, and receipt-backed CSV exports with a data dictionary. | Ready |
| Security boundary | Prevent cross-tenant or cross-host leakage | Separate marketing, authoring, and delivery hosts with explicit authentication, CORS, and token boundaries. | Planned |
Launch to reporting
The integration story is one controlled chain.
Implementation teams need to know which system owns identity, roster, assessment, attempt, score, and export records at every step. QFlowLearn documents that path before launch so there is less ambiguity during setup, testing, and support.
- Institution launches from LMS, SSO, roster target, Deep Linking placement, or direct assignment.
- QFlowLearn resolves tenant, role, learner, assessment version, accommodations, and delivery policy.
- Delivery runtime starts the attempt from an immutable package and records attempt events.
- Submission issues a durable receipt, then scoring, export, AGS grade return, and reporting run downstream.
Integration evidence
Add launch, roster, and export samples to the packet.
The integration packet should include the LTI launch sequence, Deep Linking sample, AGS score passback proof, NRPS membership read, OneRoster import report, result export sample, and security boundaries.