Mango for K-12 · For IT
Rosters that sync, logins that already work
Your students shouldn't create accounts, and your help desk shouldn't absorb the fallout when they do. Mango provisions from your student information system, launches through the identity provider you already run, and is set up by our team with yours before term starts.
Rostering & sign-on
Accounts come from your SIS, not from a sign-up form
Five routes in, and the one you use decides how little anyone has to do by hand.
Roster sync from your SIS
Users, classes and student rosters sync from common student information systems in a FERPA-compliant mode. Mango is a Certified Clever Partner. Class and enrolment changes carry through automatically, so a timetable change in the SIS is not a second job here.
- Clever · ClassLink
Nobody self-registers
Admin, teacher and student accounts are created from the SIS rather than signed up for. That removes the two things that usually sink week one of a rollout: a sign-up funnel for children, and a queue of accounts in the wrong class.
- Auto-provisioned
Single sign-on
Students reach Mango through the identity provider they already use. LTI Advantage covers launch from your LMS, and SAML 2.0 is available where you'd rather federate directly.
- LTI 1.1 & 1.3 · SAML 2.0
Interoperability certification
Mango is 1EdTech Certified (formerly IMS Global) for LTI Advantage Complete, the credential an interoperability review asks for by name, rather than a claim of general LTI support.
- 1EdTech · LTI Advantage Complete
If you have no SIS integration
A standard data upload is the supported fallback, and plenty of districts run on it. It is worth naming your route early, because it decides how much reporting rollup you get.
How that affects reporting- Standard data upload
Delivery
However your district is set up
Mango is fully web-based and cloud-hosted, with nothing to install locally. What changes between districts is how the curriculum and the lesson launch reach a student.
The LMS in production use
Canvas is where Mango's LMS integration is established rather than tested. Curriculum arrives as Common Cartridge files you import, and lessons launch in place through LTI so a student never leaves the course they're in.
Common Cartridge import for Mango Fresco
Lesson deep-linking, so an assignment points at a specific lesson
LTI 1.1 and 1.3, with LTI Advantage Complete certification
Launch from the LMS you already run
Because the certification is LTI Advantage Complete rather than a per-vendor integration, an LTI-capable platform can launch Mango and pass identity through without bespoke work on either side.
Works against LTI 1.1 and 1.3
Identity passed from your platform, with no separate Mango password
Set up with your team rather than handed over as documentation
The web app, plus whatever you already have
Districts without an LMS use the Mango web app directly, alongside iOS and Android. The platform is fully cloud-hosted with no local install, so there is nothing to package or push to a device fleet.
Web, iOS and Android, all cross-platform
No local installation and no per-user licence caps
Curriculum delivered as PDF and PowerPoint bundles
Security & privacy
What a district review asks for
Identity and access
SAML 2.0 · SSO
Single sign-on against your own identity provider, set up by our integrations team with yours before launch. Access is least-privilege, and staff take data-privacy training annually.
Student data privacy
FERPA · COPPA
For education customers, FERPA and COPPA commitments are binding through the School Terms of Service before anyone gets platform access.
Privacy commitments
GDPR · CCPA
We do not sell user information. A data-protection agreement is standard, and we negotiate the addendum your counsel needs rather than asking you to accept ours.
Accessibility
WCAG 2.1 AA alignment
Web, iOS and Android are designed and continuously improved to align with WCAG 2.1 AA. We run regular third-party accessibility evaluations and work with an ADA consultant on ongoing remediation.
Getting set up
How the work actually lands
The short version: it happens before the academic year, and our team does it with yours.
- 1
Scoping with your IT team
Mango's integrations team works out which route fits what your district actually runs, whether that is Clever, ClassLink, LTI through your LMS, SAML, or a standard data upload. This is a conversation with your staff, not a form.
- 2
Set up before the term starts
SSO and rostering are configured ahead of the academic year rather than during it. That timing is deliberate: the first week of term is the worst possible moment to discover an identity mismatch.
- 3
Nightly syncs, then left alone
Once running, roster data syncs automatically. Enrolment changes flow through without a ticket, and a dedicated K-12 data integration specialist stays available rather than handing you off.
- 4
Reporting follows your configuration
How accounts were provisioned decides how much of the district rollup you see. Worth confirming what your setup supports while you can still change it.
Who owns what
Where the line sits between your team and ours
Worth being explicit about, because the split isn't the same as it is for other kinds of customer.
Mango's integrations team owns setup
Rostering and SSO configuration is done by Mango's team with yours, not delegated to you as a self-serve settings page. K-12 admin accounts manage users, groups and reporting. Integration settings are not among them.
Your team owns the identity source
Which SIS or identity provider is authoritative, and who is in it, stays yours. Mango consumes that rather than becoming a second place where account data has to be kept true.
Data handling is contractual, before access
FERPA and COPPA commitments are binding through the School Terms of Service before anyone gets platform access, and a data-protection agreement is standard. We negotiate the addendum your counsel needs rather than asking you to accept ours.
Deletion and retention
Customer data is logically separated from other processed data, deletion is requested through a web form, and deleted data cycles out of backups within 365 days. We do not sell user information.
Accessibility
How we approach accessibility, and what it covers
Web, iOS and Android are designed and continuously improved to align with WCAG 2.1 AA. Regular third-party accessibility evaluations are part of our product development cycle, and we work with an ADA consultant on ongoing remediation.
Coverage is per product rather than blanket: that work is for the core platform, and our add-ons are not covered by it. You can read our accessibility statement in full. If an accessibility review is part of your approval, tell us which products you're considering and we'll tell you exactly what documentation exists for each.
Send us your integration questions
Tell us which SIS, identity provider and LMS your district runs, and we'll tell you what setup looks like before you commit to anything.