What the integration does
Sync iPads and Macs
Pulls both Computers and Mobile Devices from Jamf Pro in one job. Pagination handled, large fleets supported.
Match on serial
Existing HQ devices update in place. Nothing duplicates. Run sync as often as you want.
Optional Lost Mode
Parent files a lost or stolen claim, KBS HQ asks Jamf to flip Lost Mode. Opt-in, off by default.
How it works
- 1
In Jamf Pro, create an API role with read access to Computers and Mobile Devices. If you want write-back, add permission to update notes and enable Lost Mode.
- 2
Create an API client tied to that role. Note the client ID and client secret.
- 3
In KBS HQ, open Integrations, paste your Jamf Pro URL, client ID, and client secret. We verify the OAuth handshake live before saving.
- 4
Click Sync devices. iPads and Macs land in the Devices tab. Re-sync any time. Optionally enable write-back per district.
Why IT directors care
One source of truth per device
Your asset record in Jamf is the spine. KBS HQ extends it with coverage, claims, and the parent relationship without forking the data.
No CSV reconciliation
When a new building rolls out 600 iPads, Jamf enrolls them and a sync brings them into KBS HQ. Coverage offers go out to parents the same day.
Why K-12 IT directors pair Jamf Pro with KBS HQ
Jamf Pro is the gold standard for managing iPads and Macs in K-12. It handles enrollment, configuration profiles, app distribution, restrictions, and the security posture your district needs. What it does not do is run a coverage program. Jamf is not a ticketing system, not a parent billing platform, and not a repair workflow. That is the gap KBS HQ closes.
The integration pulls Computers and Mobile Devices from your Jamf Pro server using a scoped API role and a dedicated API client. Serial numbers, models, assigned usernames, asset tags. Everything is matched to existing KBS HQ records by serial so nothing duplicates. Pagination is handled, so a fleet of 8,000 iPads syncs as cleanly as a fleet of 200.
From there, KBS HQ runs the program a Jamf admin cannot run inside Jamf. Parents enroll. Claims get filed against real device records. Repairs get tracked. End of year reporting writes itself. When write back is enabled, the loop closes the other direction too. A claim opens, a note lands on the Jamf device record. A parent reports an iPad lost or stolen, KBS HQ asks Jamf to flip Lost Mode with the return message you configured. You do not lose visibility, you gain it.
What Jamf does vs what KBS HQ does
Two systems, one device record. Here is the division of labor we recommend, and what the integration keeps glued together for you.
| Job | Jamf Pro | KBS HQ |
|---|---|---|
| Device enrollment and config | Owner | Reads the result |
| Coverage and parent billing | Not its job | Owner |
| Claim intake | Not its job | Owner |
| Lost Mode on a real loss event | Executes | Triggers (opt in) |
| Repair routing and fulfillment | Not its job | Owner |
| Year end coverage reporting | Not its job | Owner |
Use cases we see most often
1:1 iPad districts K-2
High damage rate fleets where coverage and parent comms make or break the program. Lost Mode write back is a game changer.
Mac labs and faculty devices
Faculty MacBook Pros and creative lab Macs covered alongside the student iPad program in one dashboard.
Mixed Apple and Chromebook districts
Pair Jamf Pro with the Google Admin integration so one KBS HQ instance covers every device the district owns.
Lost and stolen heavy buildings
When 30 percent of claims are loss or theft, the Lost Mode write back saves your team hours of manual lock work.
Security and isolation
Scoped API role
Read Computers and Mobile Devices only. Write back adds update notes and Lost Mode, nothing else. Your Jamf admin sees exactly what we can and cannot do.
Per district credentials
Every district connects its own Jamf instance with its own API client. AES 256 GCM at rest. No shared tenants, no cross district data leakage.
Rotate or revoke any time
Disable the API client in Jamf and the integration stops cold. Disconnect inside KBS HQ and the credentials are wiped from our database immediately.
Related resources
Frequently asked questions
What does the Jamf integration sync?+
Computers (Macs) and mobile devices (iPads) from your Jamf Pro server. Serial number, model, assigned username, and asset tag. KBS HQ matches by serial number so existing records stay linked.
Jamf Pro or Jamf School?+
v1 supports Jamf Pro. Jamf School is on the roadmap. Most K-12 districts run Jamf Pro, especially at scale.
What permissions does it need?+
An API role with read access to Computers and Mobile Devices, paired with an API client. Optional write-back needs permission to update notes and enable Lost Mode. We never touch anything outside what is needed.
How does Lost Mode work with a claim?+
If a parent files a lost or stolen claim and write-back is enabled, KBS HQ can ask Jamf to put the iPad into Lost Mode with a return message. This is opt-in, off by default.
Will parents file claims through Jamf?+
No. Parents file claims in KBS HQ, where the workflow is built for them. The integration keeps Jamf updated with what is happening to the device, so your IT team sees one story across both systems.