Skip to main content

JAMF Pro

JAMF Pro enables Apple device data synchronization from your JAMF Cloud instance. This integration is intended for districts that manage macOS, iOS/iPadOS, and tvOS devices through JAMF Pro and want richer device detail inside Manage1to1 without changing how inventory is managed.

Shared setup options

Connection, Sync Options, Writeback, Device Import, and Removed-Device Handling behave the same across every MDM — Common Setup Options explains each, including how Device Import routes unknown devices into a review queue instead of adding them automatically. This page covers what's specific to JAMF Pro.

info

Manage1to1 supports JAMF Cloud instances only. On-premise JAMF Pro servers are not supported.

Before You Start

To configure JAMF Pro integration, you will need:

  • Administrator access to your JAMF Cloud instance
  • The URL of your JAMF Cloud instance (e.g., https://yourschool.jamfcloud.com)
  • An API Client with appropriate permissions (see below)

Step 1: Create API Credentials in JAMF Cloud

Manage1to1 connects to JAMF Cloud using API Client Credentials (OAuth2).

Create an API Role

  1. Log in to your JAMF Cloud instance
  2. Navigate to Settings → System → API Roles and Clients
  3. Click New under API Roles
  4. Name the role (e.g., "Manage1to1 Integration")
  5. Assign the following Read privileges:
PrivilegePurpose
Read ComputersSync macOS device data (model, OS, storage, security, apps)
Read Mobile DevicesSync iOS/iPadOS and tvOS device data
Send Computer Remote Lock CommandRequired only if using Device Disable for Macs
Send Mobile Device Remote Lock CommandRequired only if using Device Disable for mobile devices
Send Mobile Device Lost Mode CommandRequired only if using Lost Mode
Update UserRequired only if using Checkout Writeback
tip

Start with just Read Computers and Read Mobile Devices. You can add the optional permissions later if you enable Checkout Writeback, Device Disable, or Lost Mode.

Create an API Client

  1. Under API Roles and Clients, click New under API Clients
  2. Name the client (e.g., "Manage1to1")
  3. Assign the API Role you just created
  4. Enable the client
  5. Note the Client ID and Client Secret — you'll need these in Manage1to1
warning

The Client Secret is only displayed once when the client is created. Copy it immediately and store it securely. If lost, you'll need to regenerate the secret.

Step 2: Activate JAMF Pro in Manage1to1

Navigate to Settings → MDM Settings in Manage1to1.

Locate the JAMF Pro tile and select Activate.

Step 3: Configure the Connection

After activating, you will be prompted to enter your JAMF Pro connection details:

  1. JAMF Pro URL — Enter your JAMF Cloud URL (e.g., https://yourschool.jamfcloud.com)
  2. API Client ID — Enter the Client ID from Step 1
  3. API Client Secret — Enter the Client Secret from Step 1
  4. Select Test Configuration to verify the connection
  5. Save the configuration

If the test succeeds, Manage1to1 can communicate with your JAMF Cloud instance.

Step 4: Sync Device Data

After configuration, device data will begin syncing automatically. Manage1to1 syncs with JAMF Pro periodically throughout the day.

You can also view the latest JAMF Pro data for any individual device by opening the device info panel and selecting Refresh Now.

info

Manage1to1 syncs JAMF Pro data only for active devices. Devices with a status that has auto-hide enabled (e.g., Released, Retired) are excluded from sync to avoid unnecessary API calls for devices no longer in use.

important

A device must exist in Manage1to1 first (with a matching serial number) before data will sync. Devices that exist only in JAMF Pro are not automatically imported into Manage1to1.

What Data Syncs

Manage1to1 pulls comprehensive device details from JAMF Pro. The data available varies by device type:

All Device Types

DataDescription
Device NameThe name assigned to the device in JAMF
ModelFull model name (e.g., "MacBook Air (M1, 2020)", "iPad (A16)")
OS VersionOperating system version and build number
Last Check-InWhen the device last contacted JAMF Pro
IP AddressLast known IP address
WiFi MAC AddressDevice wireless MAC address
SupervisedWhether the device is supervised
ManagedWhether the device is under MDM management
OwnershipDevice ownership level (Institutional or Personal)
Enrollment MethodHow the device was enrolled (PreStage/DEP, User-Initiated, etc.)
Configuration ProfilesNumber of profiles installed on the device

macOS Computers (MacBooks, iMacs, Mac Minis, etc.)

DataDescription
ProcessorChip type and core count (e.g., "Apple M1 (8-core)")
MemoryInstalled RAM
StorageDisk capacity, used space, and percentage (shown as a progress bar)
Battery LevelCurrent charge percentage (laptops only — not shown for desktops)
Battery HealthBattery condition — Normal, Service Recommended, etc. (laptops only)
FileVaultDisk encryption status
SIPSystem Integrity Protection status
GatekeepermacOS security gate status
FirewallWhether the firewall is enabled
Activation LockWhether Activation Lock is enabled
Installed AppsNumber of applications installed

iOS/iPadOS Devices (iPads, iPhones)

DataDescription
StorageDevice capacity, used space, and percentage (shown as a progress bar)
Battery LevelCurrent charge percentage (shown as a progress bar)
Battery HealthBattery condition — Normal, Service Recommended, etc.
PasscodeWhether a passcode is set on the device
Activation LockWhether Activation Lock is enabled
Installed AppsNumber of applications installed

tvOS Devices (Apple TVs)

Apple TVs sync basic information (name, model, OS version, IP, profiles) but do not report storage, battery, or app data.


This data appears on the device profile in Manage1to1 and is used to power MDM Statistics and Reports.

Matching Behavior

JAMF Pro sync matches devices by serial number. Matching is case-insensitive — a serial entered as f0c65qynw1 in Manage1to1 will match F0C65QYNW1 in JAMF Pro.

For a device to sync:

  1. The device must exist in Manage1to1
  2. The serial number in Manage1to1 must match the serial number in JAMF Pro
  3. The device must not be hidden (devices with an auto-hide status are skipped)

If a device does not match, Manage1to1 skips it rather than creating a new record. This protects districts from inventory drift caused by old or retired devices still present in JAMF Pro.

Optional Features

Checkout Writeback

When enabled, Manage1to1 updates the assigned user field in JAMF Pro whenever a device is checked out or checked in. This keeps JAMF Pro user assignments in sync with your Manage1to1 checkout records.

Requires: Update User permission on the API role.

Device Disable

When enabled, administrators with the appropriate Manage1to1 permissions can remotely lock a device directly from Manage1to1. This sends a lock command through JAMF Pro.

  • For macOS computers, this sends a device lock command
  • For iOS/iPadOS devices, this enables or disables Lost Mode

Requires: Send Computer Remote Lock Command and/or Send Mobile Device Remote Lock Command permissions on the API role.

Lost Mode

When enabled, marking a device as lost in Manage1to1 will automatically enable Lost Mode on the device through JAMF Pro. You can configure a custom message that displays on the device's lock screen.

Lost Mode is supported on supervised iOS/iPadOS devices. macOS devices receive a lock command instead.

Requires: Send Mobile Device Lost Mode Command permission on the API role.

Sync Building From MDM

Normally a device's building is owned by Manage1to1 — it's set at check-out and through your inventory. If your source of truth for device location is JAMF Pro instead, turn on Sync Building From MDM and each sync will set the device's Manage1to1 building from its JAMF Pro building. Manage1to1 matches the JAMF building name to your buildings (tolerant of small differences like "Lincoln HS" vs "Lincoln High School").

Two safeguards always apply: a JAMF building that's empty or doesn't match one of your buildings never clears a building already set, and the reserved Graduated building is never assigned. Every building change is recorded in your Activity Log.

Building Sync Mode controls how it applies:

  • Only fill an empty building — sets the building only when the device doesn't already have one, so it never overrides a check-out. Best when JAMF is a fallback source.
  • MDM always wins — keeps the building matching JAMF on every sync. Best when JAMF is the authoritative source of location.

This is off by default — turning it on inverts the usual ownership of building, so enable it only if your district manages location in JAMF Pro.

Common Troubleshooting

Connection test fails

  • Verify the JAMF Cloud URL is correct and includes https://
  • Confirm the Client ID and Client Secret are entered correctly
  • Check that the API Client is enabled in JAMF Cloud
  • Verify the API Client has at least Read Computers and Read Mobile Devices permissions

Devices are not syncing

  • Verify the device exists in Manage1to1 with the correct serial number
  • Confirm the device is enrolled and visible in JAMF Pro
  • Check that the device is not hidden in Manage1to1 (hidden devices are excluded from sync)
  • Allow up to one sync cycle for new devices to appear

Only one type of device syncs (for example, Macs appear but iPads don't)

Read Computers and Read Mobile Devices are two separate privileges in JAMF. If the API Role has one but not the other, only that device type syncs — the missing type never appears, and you won't find those devices in the sync review.

If your Macs sync but your iPads, iPhones, or Apple TVs don't:

  1. In JAMF Cloud, go to Settings → System → API Roles and Clients and open the API Role assigned to your Manage1to1 API Client.
  2. Confirm Read Mobile Devices is checked. If it isn't, add it and save.
  3. Run Sync Devices again — your mobile devices will now be included.

The reverse applies too: if iPads sync but Macs don't, add Read Computers to the API Role.

Some device data is missing

  • Not all fields are available for every device type — for example, desktops don't report battery, and Apple TVs don't report storage
  • Recently enrolled devices may not have all data populated until their next JAMF check-in
  • Security data (SIP, Gatekeeper, Firewall) requires the device to have completed an inventory report — newly enrolled devices may show these as blank initially

Checkout Writeback not updating JAMF Pro

  • Verify the Checkout Writeback toggle is enabled in the JAMF Pro settings
  • Confirm the API role includes the Update User permission

Related articles

Loading…