Integrations built for K-12.

Connect Manage1to1 to the MDM, SIS, payment processor, and email platform your district already uses. Every integration is purpose-built for K-12, no generic enterprise connectors that need a consultant to configure.

27 live platform integrations

8
MDM & device platforms
8
SIS & rostering providers
4
Single sign-on methods
Every tier
REST API, self-service

ClassLink Rostering certified, and one vendor-agnostic OneRoster 1.1 / 1.2 connector that works with any conforming SIS.

Showing all 31 results across 6 categories.

Device management

MDM & Device Platforms

8 integrations

We pull device data directly from your MDM so the asset record in Manage1to1 always reflects the live device, enrollment status, OU placement, last sync, hardware identifiers, without manual reconciliation. Districts whose source of truth for device location is the MDM can also have each device pick up its building from the MDM on every sync, with a mapping screen for building names that do not line up on their own. Sync is one-directional by default: nothing becomes inventory unless you approve it through the device-import review queue.

  • Google Workspace

    Chrome Device Console sync. Manage Chromebooks alongside Manage1to1 asset records, with two-way sync of OU placement, annotated user, and enrollment state. Write-back fires on every path that changes hands, single-device, Rapid, and bulk check-out/check-in, and sets the Annotated Asset ID and Location alongside the user. Devices Google reports as deprovisioned can be moved to a status you choose instead of being re-imported as new. Smart Rules can also move a managed Chromebook into the right org unit automatically as its status, building, or grade changes, with Protected OUs you mark off-limits so a rule never touches them. A grade-to-OU table applies placement on checkout and device swap without writing a rule at all, and the OU picker reads your live org units straight from the integration. Granting new scopes later, device telemetry, for example, is a re-authorization in place rather than a teardown that loses your history.

    SSODevice syncWrite-backOU automationOAuth2
  • JAMF Pro

    Pull Mac and iPad inventory from JAMF Pro into Manage1to1, including hardware identifiers, last check-in, assigned user, and extension attributes.

    Device sync
  • JAMF School

    Built for K-12 deployments of JAMF School (formerly Zuludesk). Pulls device inventory, assignment data, and class context into Manage1to1, and runs remote device actions, restart, update inventory, lock, and Lost Mode, from the device profile.

    Device syncDevice actions
  • Apple School Manager

    Replacement queue integration, when a device fails or is replaced, the new serial automatically inherits the prior device's assignment, history, and ASM enrollment.

    Replacement queue
  • Microsoft SCCM

    Bring Windows fleets into Manage1to1. Sync rich device metadata (OS, IP address, and dozens of other fields you control), use recent-login data to auto-verify devices during an audit, and run lock, restart, or remote wipe from a ticket. SCCM is poll-based, so device actions run on the agent’s next check-in.

    Device syncWindows
  • Microsoft Intune

    Cloud MDM for Windows and Surface fleets, read through Microsoft Graph. Every device that exists in both systems picks up its operating system, model, ownership, compliance state, Intune device category, storage, and last check-in right on its device profile and in MDM Statistics. Devices Intune knows about and Manage1to1 does not can be routed into the import review queue, and remote Lock, Restart, and Retire run from the device profile once you switch them on. Choose Intune over SCCM when your Windows estate is cloud-managed.

    Device syncWindowsDevice actions
  • FileWave

    Cross-platform device inventory for districts running macOS, Windows, iOS/iPadOS, Android, and ChromeOS through one MDM. Rather than a fixed field list, the integration reads a FileWave Inventory Query you build, so you decide exactly which columns come across. Reads from FileWave and changes nothing in it.

    Device syncCross-platform
  • Mosyle Manager

    Apple device sync for districts on Mosyle, with remote Lock, Restart, Wipe, and Lost Mode available from a device or ticket. Currently in beta.

    Device syncBeta

Student information

SIS & Rostering (OneRoster Certified)

8 integrations

We are ClassLink Rostering certified, and a single vendor-agnostic OneRoster 1.1 / 1.2 integration syncs students, staff, classes, and enrollments from any conforming SIS. PowerSchool and Genesis districts get dedicated, first-class integrations. Mid-year transfers and new enrollments flow in automatically, so checkout, assignment, and reporting always match your source of truth. Classes, sections, and homerooms come across as first-class roster data too, so a student’s homeroom is read from your SIS instead of maintained by hand. Beyond the standard roster fields, you can map any SIS metadata key onto a Manage1to1 custom field, so values like free/reduced status, cohort, or bus route arrive with the nightly sync and stay current. Districts without a conventional SIS feed can roster from their Microsoft directory instead.

  • PowerSchool

    First-class PowerSchool integration. Sync students, staff, and demographics automatically and keep up with mid-year enrollment changes, without hand-exporting and uploading CSV files.

    SIS sync
  • Genesis

    First-class Genesis integration. Sync students and staff automatically, and pass device fees and fines back to Genesis so families settle balances where they already pay. Each line carries its own Fee or Fine type from your mapping table, whole fee categories can be marked optional rather than required, deleting a fee or fine reflects through to Genesis, and editing an invoice pushes the change across almost immediately instead of waiting for a sweep.

    SIS syncFee passback
  • OneRoster (any provider)

    One vendor-agnostic OneRoster 1.1 / 1.2 integration that works against any conforming provider. Adding a new OneRoster-speaking SIS no longer means building a one-off connection. Classes, sections, and homerooms sync alongside students and staff, as an opt-in task that runs in the background and refreshes on the same daily schedule.

    OneRosterClasses + homerooms
  • Infinite Campus

    OneRoster-based sync of students, staff, schools, classes, and enrollments. Compatible with Infinite Campus OneRoster export.

    OneRoster
  • Skyward

    OneRoster sync for Skyward SMS 2.0 and Qmlativ. Keep your Manage1to1 roster aligned with Skyward without manual CSV imports.

    OneRoster
  • Veracross

    Roster students and staff directly from Veracross, with a guided setup preset. Built for the independent and private schools that run Veracross as their system of record.

    SIS sync
  • Microsoft Entra ID (Azure AD)

    Roster students and staff from your directory instead of a SIS feed, read through Microsoft Graph. Entra has no notion of student versus staff, so you point Manage1to1 at one group for each and nested groups are included. This is the path for districts whose on-premises Active Directory already synchronizes to Entra through Azure AD Connect, with nothing to install on-site.

    Directory syncMicrosoft Graph
  • ClassLink

    Fully ClassLink Rostering certified. SSO and roster sync in one integration, staff and students sign in with ClassLink, rosters update automatically.

    Rostering certifiedSSO

Identity & sign-in

Single Sign-On

4 integrations

Staff and students sign in with the identity provider your district already runs. Administrators can additionally sign in through enterprise SAML.

  • Google Workspace

    OAuth2 single sign-on for staff and students. The same connection powers device sync and email-to-ticket.

    SSOOAuth2
  • Microsoft 365 / Entra ID

    OAuth2 single sign-on for districts standardized on Microsoft 365 and Entra ID.

    SSOOAuth2
  • ClassLink

    One-click sign-in from the ClassLink LaunchPad, paired with certified roster sync.

    SSO
  • SAML 2.0

    Enterprise SAML single sign-on for administrator access, for districts on Okta, Entra, OneLogin, ADFS, Ping, or Shibboleth. Configure more than one identity provider per district, say one for staff and one for contractors, and each gets its own sign-in button.

    SSOAdminMulti-IdP

Payments

Online Payments & Invoicing

2 integrations

Districts that bill families for device fees, insurance, or damage charges can collect payments online, directly from the parent portal, without setting up a separate merchant account.

  • ConnexPoint

    Vanco's ConnexPoint platform (formerly RevTrak). The K-12-native payment processor most districts already use for cafeteria, athletics, and registration fees. Charges, refunds, and reconciliation flow into Manage1to1 invoices.

    Online payments
  • PayPal

    PayPal Checkout for districts that prefer a generic payment processor or need a backup option alongside ConnexPoint.

    Online payments

Email & messaging

Email Integrations

5 integrations

Tickets from email, notifications to parents, transactional emails to staff, we connect directly to your school email environment. Every district also gets its own dedicated inbound email-to-ticket address, so replies file straight back onto the right ticket. Outbound family mail can go out from your own verified domain, under your own branding.

  • Google Workspace (Gmail)

    OAuth2-based connection, no app-password workarounds, no third-party email relay. Tickets auto-create from inbound mail, replies thread back to the ticket.

    OAuth2SSO
  • Microsoft 365 (Outlook)

    OAuth2-based connection for districts running Microsoft 365 or Exchange Online. Same inbound ticketing and threading behavior as Google.

    OAuth2SSO
  • POP3 / IMAP

    Fallback for any other mail provider. Pull tickets from any mailbox that supports POP3 or IMAP.

    Universal
  • Mailgun

    Districts already running a Mailgun account can send outbound notifications, ticket replies, and parent communications through it instead of the built-in delivery service.

    Outbound email
  • Your own verified sending domain

    Invoices, receipts, and family notices can be sent from a verified subdomain of your own district domain rather than a domain shared across districts, with SPF, DKIM, and DMARC in place. Your district then builds its own delivery reputation, so another district’s sending can never drag yours down, and families see your address in the From line. Messages carry your logo and drop our branding entirely, families get a standards-compliant one-click unsubscribe, and the queue paces volume per recipient domain so a start-of-year invoice run lands smoothly instead of tripping a spam filter.

    SPF/DKIM/DMARCWhite-labelDeliverability

Build your own

REST API, Self-Service for Every District

4 capabilitys

API access used to be something our team switched on district by district. It is now self-service and included at every pricing tier: an administrator issues their own scoped tokens under Settings → Integrations → API Tokens, and each token grants only the access you choose. The API reads and writes, so you can push devices in from a procurement system, open tickets from another tool, or feed a data warehouse without asking us for permission first.

  • Scoped API tokens

    District administrators issue and revoke their own tokens. Each one carries only the scopes you grant it, so an integration that only needs to read devices never gets the ability to write invoices.

    Self-serviceIncluded
  • Read and write the records you work in

    Create and update devices, users, tickets, incidents, buildings, and custom fields. Invoices are a first-class resource, including recording payments. Models, manufacturers, rooms, carts, parts, loaners, and fees are all readable.

    ReadWrite
  • Every write attributed and logged

    Writes are attributed to the administrator the token belongs to, recorded in the activity log, and marked as coming from the API. An integration's actions are as traceable as a person's, which is what an auditor asks about.

    Audit trail
  • Built for unattended use

    Idempotency so a retried call does not double-create, rate limiting, and de-duplication on ticket creation. Every list endpoint takes a modifiedSince filter, so a nightly job pulls only what changed since its last run instead of walking the whole district. Safe to point a cron at and leave running.

    IdempotentRate limitedIncremental

Product names and logos shown here are trademarks of their respective owners, used to identify the platforms we integrate with. Their appearance does not imply endorsement of Manage1to1.

Don't see what you need?

We build custom integrations for districts.

If your district uses an SIS, MDM, or payment processor we don't list here, talk to us. We've added integrations in response to specific district requests since 2012. We are not a 200-vendor marketplace, we are former school IT staff who actually use what we build.

See Manage1to1 connected to your stack.

Request a demo, we'll show Manage1to1 wired up to a sample MDM and SIS so you can see exactly how it would look with your district’s integrations.