Google Workspace

For Chromebook-heavy fleets, Nexus pulls your managed ChromeOS devices and user directory straight out of Google Workspace instead of asking you to check a second admin console.

How it works

Connects via a Google service account with domain-wide delegation — one-time setup, no per-user OAuth prompts or browser extension to deploy
Syncs every managed ChromeOS device (serial, model, org unit, last activity) from the Admin SDK Directory API into the same device inventory as your Windows/Linux/Apple fleet
Also syncs the Workspace user directory, so staff and student accounts tie to the same records tickets and device history already use
Read-only against Google's Directory API — sync and reporting only, no remote wipe or policy push; that stays in the Google Admin console

Live — the Chromebook and directory sync we run against our own K-12 school clients today.

Other integrations

Syncro

Moving off Syncro doesn't have to mean a hard cutover date. Nexus pulls your existing Syncro tickets in on a schedule so both systems can run in parallel until you're ready to switch.

FortiGate, Omada, Meraki & UniFi

Whatever network gear you've already standardized on across client sites, Nexus folds its monitoring into the same console as everything else — no separate vendor portal per brand.

Jamf

For clients on Apple hardware, Jamf-managed devices show up in the same unified console as everything else Nexus manages — one pane of glass across a mixed fleet.

See Google Workspace inside Nexus.

Join the design-partner cohort and we'll show you exactly how your existing stack folds into the console.