Lorraine for your institution.
For universities, training institutions, and academic departments that need Lorraine Learn with procurement-grade controls. Every control on this page is scoped and committed in writing before a single seat is provisioned, so your legal and IT teams can interrogate it first.
- Privacy
- POPIA aligned
- Identity
- SSO + SCIM
- Engagement
- Pilot-scoped
- Deployment
- SaaS or dedicated
The things procurement always asks about.
Six controls we commit to in writing on an institutional contract. The last column says how each one is settled — some in scoping with your IT and audit teams, some in the agreement itself.
| # | Control | What ships | How it is settled |
|---|---|---|---|
| 01 | POPIA-aligned DPA | A signed Data Processing Agreement aligned to POPIA, with clear controller and processor responsibilities and sub-processor disclosure. A document, not a feature — ask and we send it. | Available on request |
| 02 | SSO & directory | Okta, Entra, and Google Workspace with SCIM provisioning, so staff access is tied to your HR system rather than ours. Your identity provider is confirmed during scoping. | Configured in scoping |
| 03 | Audit logs | An audit trail of usage, exports, and admin actions, with retention and export format agreed with your internal audit team. | Scoped with audit |
| 04 | Volume & seat controls | Billing by team, department, or full organisation, with usage caps, budget alerts, and centralised admin against your signed seat count. | Set per agreement |
| 05 | Deployment options | Multi-tenant SaaS by default. Dedicated-tenant and private deployment for regulated environments are scoped per contract. | SaaS or dedicated |
| 06 | Dedicated support | A named partner for onboarding, clinical training, and integration. Support scope and severity-based response targets are written into the contract rather than published as a standing SLA. | Committed in contract |
Ask, and we send it.
Two documents your legal and procurement teams will want before a pilot starts. Neither is published, because both are marked up against your contract — so this is where you ask for them.
POPIA-aligned DPA
The Data Processing Agreement we sign alongside an institutional contract. Controller and processor responsibilities, sub-processor disclosure, and the cross-border transfer basis. Not published on the site — we issue it on request so your legal team can mark it up before anything is signed.
Request the DPASupport & response commitments
Support scope, escalation path, and severity-based response targets. General enquiries get a published one working day reply target; anything contractual is agreed with you rather than published as a standing SLA. Ask and we send the draft schedule.
Request the support scheduleFrom pilot to production in 6 weeks.
This is the plan we work to, not a customer case study. No institution has completed a full deployment yet — we will publish real numbers, named and with permission, once the first pilot finishes. If you would like to be that pilot, tell us.
- Week 1–2
Scoping
Faculty and cohort mapping, identity provider review, and the DPA in front of your legal team.
- Week 3
Pilot cohort
One department onboarded, tracks selected against the colleges your registrars actually sit. Where identity integration is in scope, this is the window we build it in.
- Week 4–5
Widen
Remaining cohorts provisioned. Department heads get the first cut of the analytics view, and we scope the admin controls against what they actually ask for.
- Week 6
Production
Seat counts fixed, billing schedule signed, named support partner and escalation path in place.
Committed in writing, before the first seat.
If a control is listed on this page, it is something we put our name to in writing before a single seat is provisioned, and something your legal and IT teams can interrogate first. Each one is configured against your signed scope during the pilot rather than handed over as a generic default, because an institution's identity provider, retention rules and seat structure are yours, not ours.
Let’s talk.
Tell us about your team, your constraints, and what you’re trying to do. We come back within one working day.