Every integration below runs on your district's own credentials, in your own tenant. We don't proxy your mail through our servers or hold a copy of your directory, which is also why your district stays the data controller for all of it.
Staff sign in with the account they already have. No second password to reset.
Single sign-on via MSAL, plus directory sync that maps users to schools and roles. School assignment can come from an extension attribute or from group membership, whichever your district already maintains. MFA stays enforced by Entra, where it belongs.
Single sign-on, plus directory sync driven by your OU structure: map an OU to a school and a role and it stays in step. Supports keyless OAuth, so districts with service-account key creation disabled by policy can still connect.
Tickets arrive the way your staff already ask for help.
Your support mailbox is polled through Graph using your own app registration. Replies thread by ticket number, attachments come across, and outbound mail is sent from your domain, so it passes your own SPF and DKIM.
The same intake and threading for Google districts, through the Gmail API on your own OAuth grant. Bulk mail, auto-replies, and no-reply senders are filtered out so newsletters never become tickets.
Staff text your help desk number to open or update a ticket, using your district's own Twilio account and number. Opt-in only, with verification. See the program terms.
The context that turns "my laptop is broken" into a serial number.
Apple device inventory (Macs, iPads, iPhones) with serial, model, OS, assigned user, and last check-in. Read-only.
Windows and mobile device inventory through Graph, same shape as Mosyle. Read-only.
Schools and users from ClassLink, PowerSchool, Infinite Campus, or Skyward. We pull only schools and users, never demographics, grades, schedules, or enrollments. There is no reason a help desk needs them.
Mirror a SharePoint library into Tech Docs so runbooks live next to the tickets that need them.
Subscribe to the help desk calendar (out-of-office coverage, scheduled maintenance, and breach deadlines) from the calendar app you already keep open.
Every integration on this page is configured with your district's credentials and can be disconnected by you at any time. For those connections your district is the data controller and we are the processor; they run through your accounts, not ours.
Full detail in the subprocessor list and the Data Privacy Agreement.
Don't see the system you run? Tell us what it is. We've added integrations because a district asked, and we'll tell you honestly if it isn't on the roadmap.
Ask about an integration