FERPA compliance
All student data handled per FERPA requirements. Cohort reporting uses anonymized data. PII access is role-scoped.
OVR IT for IT & Procurement
FERPA-Compliant. SSO-Ready. LMS-Integrated.
OVR IT is built to pass your vendor review. SAML 2.0 SSO, Canvas / Blackboard / D2L integration pathways, role-based access control, and a DPA ready for your procurement team — so IT can say yes and student affairs can get to work.
IT & procurement checklist
Everything your IT security and procurement teams need to evaluate OVR IT.
SSO / SAML 2.0
Native SSO support via SAML 2.0. Compatible with Shibboleth, Okta, Azure AD, and most campus identity providers.
LMS integration
Integration pathways for Canvas, Blackboard, and D2L. Sequencing defined during pilot scoping. API-first architecture.
Mobile-first architecture
iOS and Android apps built natively. Optimized for ADHD students — low-friction, async-friendly, no constant login friction.
Role-based access control
Disability services, student affairs, and IT admins each see only what their role permits. No shared admin views.
Data residency
Configurable data residency options. All data stored in SOC 2-compliant infrastructure. No third-party ad tracking.
PO-compatible procurement
Supports standard purchase order workflows. Pilot pricing structured for 1-term evaluation. No multi-year lock-in required at pilot stage.
Vendor security review
Security questionnaire, DPA, and BAA available for institutional review. Happy to participate in your vendor assessment process.
Preparing for a formal vendor review? Read our FERPA compliance checklist — the 12 questions universities ask before approving an edtech vendor →
Integration architecture
OVR IT slots into your existing stack without replacing it.
Identity
- Shibboleth
- Okta
- Azure AD
- SAML 2.0 IdP
LMS
- Canvas (LTI)
- Blackboard
- D2L Brightspace
- Custom API
SIS / Data
- Banner
- Colleague
- PeopleSoft
- CSV / SFTP export
Integration sequencing is defined during pilot scoping. Custom integration support available for enterprise deployments.
IT & procurement FAQ
- Does OVR IT support SSO / single sign-on?
- Yes. OVR IT supports SAML 2.0 SSO, compatible with Shibboleth, Okta, Azure AD, and most campus identity providers. SSO configuration is part of standard onboarding.
- Which LMS platforms does OVR IT integrate with?
- OVR IT has integration pathways for Canvas, Blackboard, and D2L. Integration sequencing is defined during pilot scoping. Our API-first architecture supports custom integration work where needed.
- How does OVR IT handle FERPA compliance?
- FERPA compliance is built into OVR IT's architecture — not bolted on. Dashboard reporting uses anonymized cohort data. Individual student records are role-scoped. Student PII does not appear in aggregate reporting views. A Data Processing Agreement (DPA) is available for review.
- What procurement documentation is available?
- OVR IT provides security questionnaire responses, a DPA, a BAA on request, and SOC 2 compliance documentation. Pilot agreements can be structured as standard purchase orders.
- Is multi-year licensing required?
- No. Pilots are scoped for one academic term (8–14 weeks). Full deployment agreements are structured annually. No multi-year lock-in is required at the pilot stage.
- Where is student data stored?
- All data is stored in SOC 2-compliant cloud infrastructure. No student data is used for advertising or shared with third-party commercial partners. Data residency options are configurable during enterprise procurement.
Other campus teams using OVR IT
Ready to start your vendor evaluation?
Request our security questionnaire, DPA, and SSO/LMS integration brief — everything your IT and procurement team needs to move forward.