Connect your stack in an afternoon. Keep your data in your control.

Nobody in a district needs another password. Staff and students sign in to schoolOS with the account they already use for everything else, which means adoption on day one and no credential for the help desk to reset at 7:40 in the morning. Identity stays where you already manage it.

One-click

Google Workspace

Sign in with a district Google account, with roles and schools from your org units and groups.

• Available to every district, no setup required
• Links to an existing schoolOS account by email address
• Roles and schools come from your org units and groups, so people stay in step as they move

One-click

Microsoft Entra ID

Sign in with a district Microsoft or Entra ID account, with roles and schools from your OUs and groups.

• Available to every district, no setup required
• Handles the several places Microsoft puts an email address
• Roles and schools come from your OUs, administrative units and security groups

One-click

ClassLink SSO

One-click sign-in from a district's ClassLink LaunchPad.

• Staff and students sign in with the ClassLink account they already have
• Launches from the LaunchPad tile, not only from our login page
• Matches people by their OneRoster identifier, so a rostered district connects cleanly
• Appears only for districts that turn it on, on their own subdomain

Most districts run more than one MDM: Jamf for the Macs, Google for the Chromebooks, Intune for whatever Windows is left. None of them agree on what a device is, and none of them know who's holding it. schoolOS connects to each one, pulls every device into a single asset record, and pushes your changes back out. Lock, wipe, or deprovision from the asset record instead of from three consoles. PDQ Connect fills in the Windows fleet, and Apple School Manager tells you what you bought before it ever enrolls.

One-click

Jamf Pro

Apple device management for computers and mobile devices, syncing both ways.

• Computers and mobile devices, with their full metadata
• Write-back pushes schoolOS field values into Jamf, not just reads out of it
• Lock, restart, wipe, deprovision and recovery lock, each checked against what the device can actually do
• Per-field push, pull or off, with arrows showing which way each field moves
• Runs nightly, or on demand

One-click

Google Devices

Chromebooks and other Google-managed devices from the Admin console.

• Chromebook sync with organizational unit and enrollment detail
• Disable, deprovision and delete, from the asset record or a workflow
• The same field-mapping screen as Jamf, driven by a Google field catalogue
• Runs nightly, or on demand

One-click

Microsoft Intune

Windows, iOS and Android devices managed through Intune.

• Cross-platform device sync via Microsoft Graph
• Catalogue-driven field mapping, at parity with Jamf and Google
• Compliance and enrollment state carried onto the asset record

One-click

Mosyle

Apple device management for districts on Mosyle Manager or Business.

• Device sync through Mosyle's token-header API
• Field catalogue mapped to the same asset fields as every other provider

PDQ Connect

Windows devices from one or more PDQ organizations, with their software, updates and vulnerabilities.

• Connect one PDQ organization, or several
• Every Windows device comes in with its installed software, pending updates and known vulnerabilities
• Lands in the same asset record as your Apple and Chrome devices

Apple School Manager

Every Apple device your district bought, with its order details and AppleCare coverage.

• Every Mac, iPad and Apple TV purchased through your reseller, before it ever enrolls in an MDM
• Order details on each device record
• AppleCare coverage, so you know what is covered before you open the repair

A loaner handoff usually means a tech waiting at a counter and a student waiting on the tech. With smart lockers, the ticket does the handoff. schoolOS reserves a bay, sends the student a one-time PIN, and records the pickup or drop-off against the device and the ticket the moment the door closes. Nobody has to be standing there.

LocknCharge

ForwardPass (FUYL Tower) smart lockers: tickets reserve a bay with a one-time PIN, and pickups and drop-offs update the device and the ticket.

• A ticket reserves a bay and issues a one-time PIN
• Pickups and drop-offs update the device record and the ticket on their own
• Works for loaner handouts and repair drop-offs alike

A cracked screen turns into a fine, the fine turns into a letter home, and the letter turns into a spreadsheet someone checks against the business office once a month. schoolOS posts the fine where parents already pay for lunch, and when they pay it, the fine settles itself. No reconciliation, no chasing.

MySchoolBucks

Post fines as student fees, let parents pay in MySchoolBucks, and settle fines in schoolOS automatically.

• A fine in schoolOS becomes a student fee in MySchoolBucks
• Parents pay in the app they already use
• Payment settles the fine in schoolOS with nothing to reconcile by hand

Who is out Friday is the question behind half the tickets that stall. Share the calendars your teams already keep, a PTO calendar, a maintenance schedule, a testing window, with the departments and teams who need to see them. They show up on each person's calendar page in schoolOS, and the people you choose can add to them.

One-click

Google Calendar

Share a Google Calendar, like a team PTO calendar, with departments and teams. They see it on their calendar page and can add to it.

• Pick the calendar and the departments or teams who should see it
• Shows up on their calendar page in schoolOS
• The people you choose can add events, and Google stays the source of truth

One-click

Outlook Calendar

Share an Outlook calendar, like a team PTO calendar, with departments and teams. They see it on their calendar page and can add to it.

• Pick the calendar and the departments or teams who should see it
• Shows up on their calendar page in schoolOS
• The people you choose can add events, and Outlook stays the source of truth

An AI agent is only as good as what it knows, and what your district knows is scattered. The answer to “how do I request a sub” is in a Zendesk article. The device damage policy is a PDF in a shared Drive folder. The board's acceptable use policy is a page on the website nobody has opened since 2019. schoolOS brings documents and help articles into the knowledge base schoolAgent answers from, keeps them in sync as they change, and cites the source on every answer, so people get your district's answer instead of the internet's. Nothing is written back.

One-click

Deep Web Crawl

Your district's own websites as a knowledge source.

• Crawls public pages: policies, handbooks, department pages, board documents
• Structure-aware chunking, so an answer comes back with its heading and context intact
• Re-crawls on a schedule the district sets, and only reindexes pages that actually changed
• Every answer links back to the page it came from
• Auto-crawls beyond your core site: transportation pages, BoardDocs and other board portals, Nutrislice and other menu services, athletics and activities calendars

One-click

Zendesk

Help Center articles from the sections you choose.

• Categories, sections and articles, kept in sync
• Connects from Knowledge Sources without leaving the page
• Ticket sync is planned, not built

One-click

Freshdesk

Solution articles from the Freshdesk folders you choose.

• Pick the folders, and only those solution articles come in
• Shares the Help Center tab with Zendesk. Pick one, connect, done
• Ticket sync is planned, not built

One-click

Google Drive

Shared folders and documents pulled into the knowledge base.

• Folder-scoped sync, so a district shares only what they mean to
• Documents indexed for the Co-Pilot to cite

One-click

Microsoft OneDrive

Files and folders from OneDrive and SharePoint.

• The same folder-scoped model as Google Drive
• Documents indexed for the Co-Pilot to cite

One-click

Confluence

Pages from the Confluence spaces you choose.

• Pick the spaces, and only those pages come in
• Internal runbooks and procedures become answers for staff, not for the public
• Nothing is written back to Confluence

One-click

Freshservice

Solution articles from the Freshservice folders you choose.

• Pick the folders, and only those articles come in
• Keep writing in Freshservice. schoolOS stays in sync as articles change
• Nothing is written back to Freshservice

One-click

HappyFox

Knowledge base articles from HappyFox.

• Your HappyFox knowledge base becomes a source schoolAgent answers from
• Every answer cites the article it came from
• Nothing is written back to HappyFox

Rostering is what turns an asset record into something you can act on. A device stops being a serial number and becomes the Chromebook assigned to a fourth grader at Lincoln, in Ms. Alvarez's homeroom, whose guardian should get the damage notice. Every ticket, every assignment, every workflow leans on knowing who's who. So schoolOS takes the roster however your district can give it, from a CSV someone drags into a browser to a live API, and keeps it current overnight without anyone thinking about it again.

Roster Import

One screen for every way a roster can reach schoolOS, from a hand-uploaded CSV to a live API.

• Four methods: manual CSV, flat CSV over SFTP, OneRoster bundle over SFTP, or the OneRoster API
• 30+ student information systems, each narrowing the methods offered and carrying its own quirks
• OneRoster 1.1 and 1.2, over OAuth 2, OAuth 1 or a static token
• Delta sync where the vendor reports change dates, full sync where they do not
• Runs nightly on a schedule the district sets

One-click

ClassLink Roster Server

Rosters through ClassLink's proxy, which normalizes whatever SIS sits behind it.

• Nothing for a district to enter. They grant schoolOS access in ClassLink and pick themselves from a list
• Honors ClassLink's own guidance: 10,000-record pages, backoff on rate limits
• Abandons a pull when the district's SIS writes mid-read, rather than importing a torn snapshot

All product names, logos, and brands are property of their respective owners and are used for identification purposes only.