Jamf Integration Setup

The Jamf Integration brings your organization's Apple device and user data into FMX. This allows IT teams to manage 1:1 device programs, view real-time inventory, and create tickets for devices and users— all from a single platform. Pairing this integration with SSO enables seamless onboarding and access control, ideal for education and enterprise IT environments.

NOTE: This integration supports Jamf Pro and Jamf School. The steps to set up each differ slightly. Our documentation will walk you through these differences and how to navigate them.

What You'll Unlock

• Hourly sync of user and device data from Jamf to FMX
• Unified visibility into all managed Apple devices and users
• Audit trails of device ownership, assignment, and access
• Ability to create tickets directly on behalf of devices or users
• Automations for asset assignment, user provisioning, and IT requests

1. Requirements

• FMX Account (1-to-1 Asset Manager & IT Ticketing modules recommended)
• Jamf account with admin access
• Integration access enabled in FMX (contact your FMX account manager)
• SSO (Single Sign-On) is strongly recommended for seamless user provisioning

2. FMX Setup

• Create an Integration User Type
  • Go to Admin Settings → User Types in FMX
  • Create (or copy) a user type (e.g., "FMX Integration") with:
    • Building & Resource Access
    • Equipment Access
    • User & Contact Access
    • If restricting custom field access, ensure this user type is a permitted user for all custom fields you wish to sync.
  • Tip: How to Customize User Access
• Add Required Custom Fields
  • For Devices & Computers:
    • Jamf UDID (Text field) — No equipment type restrictions are needed
    • Optional: serial number, OS version, model, etc.
  • For Users:
    • Jamf User ID (Text field) — No user type restrictions are needed
    • Optional: job title, department, etc.
  • Ensure these fields are accessible for the FMX Integration user type.
  • Tip: Adding Custom Fields
• Add/Update Equipment Types
  • Create an equipment type in FMX for each Jamf computer/mobile smart group you want to sync
  • Tip: Add Equipment Types

See a complete list of available custom fields at the bottom of this page; however, remember you only need the Jamf UDID and Jamf User ID custom fields. All others are optional.

3. Jamf Setup

Jamf Pro

• Create an API Role
  • In Jamf Pro, go to Settings → System → API Roles and Clients
  • Click + New Role and give it a name (e.g., "FMX Role")
  • Assign privileges:
    • Read Buildings
    • Read Computers
    • Read Computer Extension Attributes
    • Read Mobile Devices
    • Read Mobile Devices Extension Attributes
    • Read Smart Computer Groups
    • Read Smart Mobile Device Groups
    • Read Smart User Groups
    • Read User
    • Read User Extension Attributes
• Create API Client ID & Client Secret
  • In the API Clients tab, click + New
  • Assign the API Role you created above
  • Set Access Token Lifetime to 3600
  • Enable API Client, click Save
  • Click Generate client secret — Make sure to copy your client secret, as you will not be able to view it again after leaving this page.
• Enroll Devices/Users in Jamf Pro
  • Make sure devices and users are properly enrolled and organized in smart groups for mapping in FMX

See this Jamf article for more details.

Jamf School

• Create an API Key
  • In Jamf School, go to Organization -> Settings -> API -> Add API Key
  • For access rights, only check Read. Click Apply and copy your key for later.
• Get your Jamf School Network ID
  • Navigate to Devices -> Enroll device(s)
  • Find your MDM Server URL on this page and copy the number at the end of it. For example, if your MDM Server URL is acme.jamfcloud.com/?network=12345678, then your Network ID is 12345678.

4. Integration Setup

Step 1: Initial Configuration

• In FMX, navigate to Admin Settings → Integrations, select Jamf.

• Click Reconfigure

• This step is purely informational. Click Next.

Step 2: Jamf API Configuration

Jamf Connection

• Select either Jamf School or Jamf Pro under the Jamf Type dropdown, depending on which Jamf product you are using.
• Jamf School
  • Input your Jamf Base URL. This is typically the website you use to log into Jamf and usually looks like https://yourorganization.jamfcloud.com. 
  • Input the Jamf School Network ID and Jamf School API Key that you generated above.
  • Check Sync Users if you would like to sync users from Jamf to FMX.
  • Check Sync Devices if you would like to sync devices such as smartphones or laptops from Jamf to FMX.
• Jamf Pro
  • Input your Jamf Base URL. This is typically the website you use to log into Jamf and usually looks like https://yourorganization.jamfcloud.com. 
  • Input the Jamf Pro Client ID and Jamf Pro Client Secret that you generated above.
  • Check Sync Users if you would like to sync users from Jamf to FMX.
  • Check Sync Pro Computers if you would like to sync computers, such as MacBooks, from Jamf to FMX.
  • Check Sync Pro Mobile Devices if you would like to sync mobile devices, such as iPhones or Apple Watches, from Jamf to FMX.

FMX Connection

• Hostname — the text before .gofmx.com in your FMX URL (e.g., fmxschool from https://fmxschool.gofmx.com/)
• API User Email — email address of your FMX integration user (e.g., jamfsyncer@gofmx.com)
• Password — password for the FMX integration user
• All integrations are required to have their own dedicated API user (e.g., "Jamf Syncer") within FMX for the integration to use. This user should use the FMX Integration user type you created in the prior steps. This user type must have permissions for all equipment types, custom fields, and the ability to create/update/retire equipment. Using the same user credentials across multiple integrations can cause data from third parties to never sync to FMX. 
• Click Next to continue

Step 3: Jamf Entity Mapping

If you are using Jamf Pro, you will see a tab for Computers and Mobile Devices. If you are using Jamf School, you will only see a tab for Devices. Besides this small difference, the steps to set up either integration are otherwise identical.

• Select Computers / Mobile Devices or Devices, depending on which Jamf product you are using.
• Click the + button to add a mapping. Each mapping consists of the following options, which define how data will sync from Jamf to FMX

  • Jamf Computer Group defines which group in Jamf this mapping should apply to. Mappings are applied from top to bottom. If you have Jamf devices belonging to multiple groups, it is generally recommended to put the broadest Jamf groups at the top and more specific groups at the bottom so that mappings are properly applied. Mappings can be moved up or down using the arrows next to the Trash icon. (See screenshot below)

    

  • FMX Equipment Type defines which equipment type this Jamf group should be mapped to. Whichever equipment type(s) you select for this option must have access to the Jamf UDID custom field you created earlier.
  • Default Building defines which building equipment synced from Jamf should be assigned to. It is optional.

    • Warning: If you opt not to set an option here, ensure all users who could possibly be assigned equipment from Jamf in FMX have the Can access records with no building option selected in FMX -> Admin Settings -> User Types -> <user type> -> User Type  

      

  • Override Existing Equipment Building determines if the integration will change the building a piece of equipment is assigned to on update. (The building selected in Default Building will always be applied to equipment creation.)
  • Override Existing Equipment Type determines if the integration will change the equipment type of a piece of equipment on update. (The building selected in FMX Equipment Type will always be applied to equipment creation.)
• Select the Users tab at the top.
  • Click the + button to add a mapping. Each mapping consists of the following options, which define how data will sync from Jamf to FMX.
    • Jamf User Group defines which group in Jamf this mapping should apply to. Mappings are applied from top to bottom. If you have Jamf users belonging to multiple groups, it is generally recommended to put the broadest Jamf groups at the top and more specific groups at the bottom so that mappings are properly applied. Mappings can be moved up or down using the arrows next to the Trash icon. (See screenshot above)
    • FMX User Type defines which user type this Jamf group should be mapped to. Whichever equipment type(s) you select for this option must have access to the Jamf User ID custom field you created earlier.
    • Sync as defines if users from this Jamf group should be synced as Users or Contacts in FMX.
    • Accessible Buildings defines which accessible buildings users from Jamf should be assigned in FMX.
    • Override User Accessible Buildings determines if the integration will change the accessible buildings a user is assigned on update. (Whichever building(s) were specified in Accessible Buildings will always be applied to user creation.)
    • Override Existing User Type determines if the integration will change the user type a user is assigned on update. (Whichever user type was selected in FMX User Type will always be applied to user creation.)

When finished, click Next.

Step 4: Field Mapping

The Jamf Field Mapping page defines which fields from Jamf should be mapped to which custom fields in FMX. Most are not required, though a few are:

• Tag Field: (Computers and Mobile Devices from Jamf Pro, Devices from Jamf School) This field selects which field from Jamf should be the tag field for equipment. While you can select most options here, we recommend choosing a field that will almost always be populated, such as General > Name
• UDID: (Computers and Mobile Devices from Jamf Pro, Devices from Jamf School) Select the Jamf UDID field you created earlier for this option.
• User ID: (Users) Select the Jamf User ID custom field you created earlier for this option.

No other fields are required, though you can opt to add as many or as few as you like using this page.

Once finished, click Finish to save your settings and enable your integration.

Frequently Asked Questions

How often does device data sync?

• Every hour

Can I update device info in FMX and have it reflect in Jamf?

• No. This integration provides a one-way sync from Jamf to FMX.

What happens if I add or remove devices/groups in Jamf?

• New devices in synced groups will appear in FMX after the next sync; devices removed from Jamf will be retired in FMX. 

What happens if I add or remove users in Jamf?

• Users removed in Jamf will have their corresponding user in FMX deleted.

Optional Custom Fields

Below are optional custom fields you can sync from Jamf to FMX. These need to be text fields (unless otherwise specified) that are not required for equipment. These fields can be added later, and the integration can be updated to sync them.

Jamf Pro

Jamf School

Tip: Adding Custom Fields