> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/integrations-store/device-management/jamf-pro-integration.md).

# Jamf Pro Integration

You can integrate your Jamf Pro Cloud account with Asset Panda Pro to support data synchronization between the applications. The integration keeps your asset records accurate and up to date by continuously importing device and user information data from Jamf Pro into Asset Panda Pro. Supported fields can also be transferred from Asset Panda Pro back to Jamf Pro.

{% hint style="info" %}
Jamf Pro is a third-party application. Asset Panda does not control updates made by Jamf Pro. For more information on Jamf Pro, see Jamf Pro Product Documentation and [Jamf Pro | Mobile Security | Casper Suite](https://www.jamf.com/products/jamf-pro/). 
{% endhint %}

You perform the following steps to Integrate Jamf Pro with Asset Panda:

* **Enable Jamf Pro:** Connect the Jamf Pro account to fetch data. 
* **Configure Asset Panda Integration:** Steps to configure and map the Jamf Pro data fields within Asset Panda. 
* **Ensure Data Accuracy:** Ensure that the data fetched from Jamf Pro is accurately mapped and stored in Asset Panda. 

***

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* Active Jamf Pro Cloud account
* Active Asset Panda Pro account with administrator access to configure the integration
* Permissions to configure integrations in both Jamf Pro and Asset Panda Pro
* Unique fields to support syncing:
  * Computer devices: unique Serial Number or Asset Tag
  * Users: unique Email Address&#x20;

***

## Set up the Jamf Pro integration <a href="#setup" id="setup"></a>

1. Log into Asset Panda Pro with an administrator account.
2. Navigate to <img src="/files/dLHka5YWbUR3zisHLua6" alt="Settings icon" data-size="line"> **Settings** > **Account Management**.
3. Expand the appropriate account and module.
4. Click **Manage** in the **Integrations** card.
5. In the **Jamf Pro** tile, click **Add**, and then click **Edit**.&#x20;
6. To authenticate Asset Panda Pro with Jamf Pro, enter the following details:
   * **Server Hostname**: Jamf Pro URL (for example, <kbd><https://xyz.jamfcloud.com></kbd>)
   * **Username**: Jamf Pro account username. See [Jamf Pro Permissions](#permissions).
   * **Password**: Jamf Pro account password
   * **Port**: Required port number
7. Click **Test and Save Connection** to verify the authentication. If the connection fails, verify your credentials and try again.
8. Click **Continue with mapping**.
9. Specify the following information for the mapping:
   1. For **Mapping Name**, enter a descriptive name for the mapping.
   2. Select the **Collection** in Asset Panda Pro where the data is stored.
   3. Select the appropriate **External Entity** (for example, Computers or Users).
10. Map Jamf Pro fields to Asset Panda Pro. See [Jamf Pro fields](#jamf-pro-fields).

### Jamf Pro fields&#x20;

Mapping defines where each data point from Jamf Pro is placed in Asset Panda. It also determines the field that is used to uniquely identify records. This is critical for maintaining data accuracy and avoiding duplication.

| Field Name                      | Description                                           | Mapping Guidance                               |
| ------------------------------- | ----------------------------------------------------- | ---------------------------------------------- |
| Active Directory Status         | Indicates if the device is linked to Active Directory | Map for device compliance tracking,if needed   |
| Architecture Type               | Processor architecture (for example, x86, ARM)        | Map if you're categorizing by hardware type    |
| Asset Tag                       | Custom tag assigned to the device                     | Recommended for unique ID if used consistently |
| Bar Code 1                      | Primary barcode label                                 | Map if barcoding is used in inventory tracking |
| Bar Code 2                      | Secondary barcode label                               | Map as a backup barcode or alternate tag       |
| Bluetooth Low Energy Capability | Indicates support for BLE                             | Map for tracking device features               |
| Building ID                     | Identifier for asset location                         | Map to location field                          |
| Bus Speed                       | System bus speed                                      | Map if tracking hardware performance           |
| Cache Size                      | CPU cache size                                        | Map for detailed profiling                     |
| Computer Name                   | Assigned name of the device                           | Useful for display only; avoid as unique ID    |
| Department ID                   | Internal department ownership                         | Map for department-based filtering             |
| Email Address                   | User's email address                                  | Recommended unique ID for users                |
| FileVault 2 Enabled Users       | Users with FileVault access                           | Map for security compliance                    |
| Full Name                       | User’s full name                                      | Map for display; not a stable unique ID        |
| IP Address                      | Current device IP address                             | Avoid – dynamic value                          |
| Is Leased                       | Indicates leasing status                              | Map for lifecycle tracking                     |
| Is Purchased                    | Indicates if the asset was purchased                  | Map for financial reporting                    |
| Jamf Binary Version             | Version of installed Jamf agent                       | Map to verify system coverage                  |
| Jamf Pro Computer ID            | Internal unique ID assigned by Jamf Pro               | Safe and stable unique ID                      |
| Lease Expiration                | Lease end date                                        | Map for contract expiration tracking           |
| Life Expectancy                 | Expected life of the device                           | Map to plan replacements                       |
| Make                            | Manufacturer (Apple, Dell, etc.)                      | Map to vendor field                            |
| Managed                         | Whether device is under Jamf management               | Map to indicate device compliance              |
| MDM Capability                  | Indicates support for Mobile Device Management        | Map for enrollment eligibility                 |
| Model                           | Device model name                                     | Map to categorize asset types                  |
| Model Identifier                | Manufacturer's model ID                               | Map for technical reference                    |
| NIC Speed                       | Network card speed                                    | Map if tracking network capabilities           |
| Number of Processors            | Total processor count                                 | Map for performance or hardware reports        |
| Operating System                | OS installed on the device                            | Map for inventory or software compliance       |
| Operating System Build          | Specific build number of the OS                       | Map to ensure version compliance               |
| Optical Drive                   | Presence/type of optical drive                        | Map if relevant to asset profile               |
| Phone Number                    | User's contact number                                 | Avoid – may change or duplicate                |
| Platform                        | OS platform (e.g., macOS, iOS)                        | Map to separate desktop vs. mobile assets      |
| PO Date                         | Purchase order date                                   | Map for procurement history                    |
| PO Number                       | Purchase order reference                              | Map for financial linking                      |
| Position                        | User’s job title                                      | Map for HR alignment                           |
| Primary MAC Address             | Main MAC address of the device                        | Use with caution as unique ID                  |
| Processor Speed                 | CPU speed in GHz                                      | Map for hardware tracking                      |
| Processor Type                  | CPU model (Intel, Apple Silicon, etc.)                | Map to identify chipsets                       |
| Purchase Price                  | Cost of the asset                                     | Map for value and depreciation tracking        |
| Room                            | Room/location within a building                       | Map for precise asset location                 |
| Secondary MAC Address           | Alternate MAC address                                 | Use if primary MAC not available               |
| Serial Number                   | Manufacturer serial number                            | Highly recommended for device matching         |
| SMC Version                     | Apple system controller version                       | Map for Mac-specific auditing                  |
| Supervised                      | Indicates supervision status                          | Map for compliance tracking                    |
| Total Number of Cores           | CPU core count                                        | Map for system spec reports                    |
| Total RAM                       | Installed memory size                                 | Map for hardware profile                       |
| UDID                            | Universal Device Identifier                           | Best for mobile/Apple devices                  |
| Username                        | Login username of the user                            | Not recommended as unique ID                   |
| Vendor                          | Supplier of the device                                | Map for procurement reports                    |
| Warranty Expiration             | Warranty end date                                     | Map for renewal and support planning           |

***

### Enable two-way synchronization

Optionally, you can configure two-way synchronization with Jamf Pro to enable updates made in Asset Panda Pro to be pushed into Jamf Pro to maintain consistent and up-to-date records across both systems.

Two-way sync requires a separate mapping configuration:

1. Create a new mapping.
2. Select **Sync Direction: Asset Panda → Jamf Pro.**
3. Map [supported entities and fields](#supported-entities-and-fields).&#x20;

{% hint style="info" %}
Only fields editable within Jamf Pro are supported for updates.
{% endhint %}

4. Save the mapping.
5. Run the synchronization via a manual or scheduled automation. Updates in Asset Panda Pro are reflected in Jamf Pro.

{% hint style="info" %}

* Field-level validation ensures only supported fields are updated.
* Real-time sync is not supported.
* Sync behavior depends on automation timing.
* Updates are pushed during sync execution.
* If updates occur in both systems, the system that syncs last takes precedence.
  {% endhint %}

6. Review integration logs for information about the synchronization.

***

#### Supported entities and fields

{% hint style="info" %}
The supported fields can change based on Jamf Pro API updates.
{% endhint %}

<table><thead><tr><th width="159.58984375" valign="top">Entity</th><th valign="top">Supported Field</th></tr></thead><tbody><tr><td valign="top"><strong>Buildings</strong></td><td valign="top"><ul><li>City</li><li>Country or Region</li><li>Display Name</li><li>ID</li><li>State/Province</li><li>Street Address 1</li><li>Street Address 2</li><li>Zip/Postal Code</li></ul></td></tr><tr><td valign="top"><strong>Computers</strong></td><td valign="top"><ul><li>Active Directory Status</li><li>Asset Tag</li><li>Bar Code 1</li><li>Bar Code 2</li><li>Building ID</li><li>Computer Name</li><li>Department ID</li><li>Email Address</li><li>Full Name</li><li>IP Address</li><li>Jamf Pro Computer ID</li><li>Management ID</li><li>Phone Number</li><li>Position</li><li>Primary MAC Address</li><li>Room</li><li>Secondary MAC Address</li><li>UDID</li><li>Username</li><li>Vendor</li></ul></td></tr><tr><td valign="top"><strong>Departments</strong></td><td valign="top"><ul><li>Display Name</li><li>ID</li></ul></td></tr><tr><td valign="top"><strong>Mobile Devices</strong></td><td valign="top"><ul><li>Asset Tag</li><li>Building ID</li><li>Department ID</li><li>Email Address</li><li>Full Name</li><li>Jamf Pro Mobile Device ID</li><li>Mobile Device Name</li><li>Phone Number</li><li>Position</li><li>Room</li><li>Username</li></ul></td></tr><tr><td valign="top"><strong>PreStage</strong></td><td valign="top"><ul><li>PreStage ID</li><li>Serial Number</li></ul></td></tr><tr><td valign="top"><strong>Users</strong></td><td valign="top"><ul><li>Email Address</li><li>Full Name</li><li>ID</li><li>Phone Number</li><li>Position</li><li>Username</li></ul></td></tr></tbody></table>

***

### Device Management Actions

The Jamf Pro integration supports automated device actions, enabling you to manage Jamf-managed devices directly from Asset Panda Pro.&#x20;

{% hint style="info" %}
Device management requires the appropriate permissions in Jamf Pro.
{% endhint %}

You can select **Device Management** when configuring the automation to enable the following actions:

* **Remote Lock**: Locks the device remotely
* **Erase**: Wipes device data

The actions can be triggered record updates, form submissions, or status changes and run as part of automation workflows. Results can be reviewed in integration logs.

***

## Jamf Pro permissions <a href="#permissions" id="permissions"></a>

Your Jamf Pro account must have sufficient privileges to access and sync the necessary data. You can use one of the pre-existing privilege sets or define custom permissions.

### Jamf Pro pre-existing privilege sets&#x20;

<table><thead><tr><th width="162.9921875">Privilege Set</th><th>Privilege Description</th></tr></thead><tbody><tr><td>Administrator</td><td>User can read and write the records, along with other privileges</td></tr><tr><td>Auditor</td><td>User canread and write the records (minimum requirement)</td></tr><tr><td>Enrollment Only</td><td>User cannot read or write the records (not required for integration)</td></tr><tr><td>Custom</td><td>User can set specific permissions as needed</td></tr></tbody></table>

### Jamf Pro custom privileges&#x20;

<table><thead><tr><th width="161.78515625">Entity</th><th width="118.0546875">Read</th><th>Write</th></tr></thead><tbody><tr><td>Users</td><td>Required</td><td>Required for two-way sync (when updating records from Asset Panda Pro to Jamf Pro)</td></tr><tr><td>Computers</td><td>Required</td><td>Required for two-way sync (when updating records from Asset Panda Pro to Jamf Pro)</td></tr><tr><td>Mobile Devices</td><td>Required</td><td>Required for two-way sync (when updating records from Asset Panda Pro to Jamf Pro)</td></tr><tr><td>Buildings</td><td>Required</td><td>Required for two-way sync (when updating records from Asset Panda Pro to Jamf Pro)</td></tr><tr><td>Departments</td><td>Required</td><td>Required for two-way sync (when updating records from Asset Panda Pro to Jamf Pro)</td></tr></tbody></table>