Integrations
Integrations install as Apps. Each declares typed contracts — what it supplies, what it reads, what it writes — and the platform enforces them. An App never touches the core schema directly, which is what keeps an integration from quietly becoming a dependency you cannot remove.
How Apps work
Before an App is enabled, an administrator can read exactly what it will do: which entities it reads, which it writes, and which actions it adds. Nothing is discovered afterwards.
Supplies people. Multiple sources can contribute to one person; field priority decides who wins each attribute, and disagreements land in a conflict queue instead of overwriting silently.
Authenticates people. Group claims map to roles at login through the same rule engine the core SAML integration uses.
Supplies devices and their state, reconciled against the asset register with configurable matching and lifecycle rules.
Adds buttons to records — lock this Chromebook, start a remote session. Every invocation is audited with the actor.
Declares exactly which entities the App reads and writes, in which direction. The declaration is visible before you install.
Reports upstream health into the status monitor, with suppression rules so a known outage does not flood the helpdesk.
Two systems will disagree about a person. PowerSchool says one email, Entra says another, and one of them is stale. CampusLink treats that as a resolvable conflict with a queue and a decision, rather than as whichever sync ran last.
The catalogue
Fifteen first-party Apps, installed and configured from
/Apps by an administrator — no deployment, no vendor
ticket.
Students, staff, guardians, courses, sections and class rosters, pulled through a signed CampusLink plugin installed in PowerSchool. Plugin and connector ship as a version-matched pair, and the connector refuses to run outside the window it was tested against. Also handles cohort history, site linking and grade promotion requests with admin approval.
Users and groups from Google Workspace into the core directory, through the same reconciliation engine every other identity source uses.
Chromebook inventory sync with per-state lifecycle handling, and Quick Lock, Re-enable, Deprovision and Lost Mode commands dispatched from the asset record. Serial-versus-asset-tag matching rules are configurable, because every district labels differently.
Google Workspace as a SAML 2.0 identity provider, SP-initiated.
Users and groups from Entra, optionally restricted to a single group, plus SAML sign-in with group claims mapped to CampusLink roles. Just-in-time provisioning is opt-in and always runs through reconciliation.
Windows managed-device inventory, with Quick Lock, Locate, Reboot, Retire and Wipe available from the asset record.
OneRoster federation that defaults to link-only: it attaches ClassLink and OneRoster identifiers to people who already exist rather than creating new accounts. Terms, classes, teachers and enrolments come across for the sessions that cover today. Sign-in from the ClassLink launchpad via SAML.
Last-seen location, access point and connection history for a device, looked up by MAC from the Meraki Dashboard API. Surfaced on the asset panel — which is how a missing laptop stops being a mystery.
Remote desktop sessions against a self-hosted MeshCentral server, launched from an asset or a ticket rather than from a separate console.
A Start Remote Session button on helpdesk tickets for managed Chromebooks. Every click is written to the audit log.
Print balances, quotas and recent job history on user profiles and tickets, with per-user quota adjustment and printer inventory.
Distribute district policies — AUP, BYOD, FERPA, code of conduct — with versioning, acceptance tracking, an acceptance banner, automated reminders and compliance reports.
Aggregates vendor status pages (Statuspage.io, Statuspal, Better Stack, RSS) into one surface, with a district banner and helpdesk ticket suppression — so a Google outage does not generate two hundred tickets your team has to close by hand.
Checkout for asset damage fees and facility rental invoices, with mark-paid and refund handled inside the module that raised the charge.
A signed, read-only bridge feeding buildings, rooms and staff to the Algo intercom and mass-notification platform, plus an idempotent inbound sink for drill, alert and device events. HMAC-SHA256 per request with a replay cache; credentials are issued and disabled from the admin UI.
Your own systems
Districts run systems nobody anticipated. There are three ways in, and all three are scoped by the permissions of whoever set them up.
Three admin surfaces exist because integrations fail quietly, and a sync that stopped three weeks ago is worse than one that never ran.
CampusLink is independently developed by Melton Electronics and is not affiliated with, endorsed by, or sponsored by any of the vendors named on this page. Product names are used only to identify the systems CampusLink integrates with, through each vendor's published interfaces. All trademarks are the property of their respective owners.
Send the list — SIS, directory, MDM, print, access control. We will say plainly which are supported today, which need an App, and which are genuinely a problem.