Pult Presence Docs
MDM IntegrationsJumpCloud

Overview

What data Pult syncs from JumpCloud, what it enables, and what you need.

Pult Presence integrates with JumpCloud to sync managed device data. The integration is read-only: Pult periodically fetches the device inventory and uses it to associate devices with users.

JumpCloud covers devices running macOS, Windows, and Linux. Mobile devices (iOS, Android) are not included in the sync.

What data is synced

For each device that has an active primary user assigned, Pult pulls:

  • Device serial number
  • WiFi MAC address (from JumpCloud System Insights)
  • User email (from the device's primary user)
  • Device metadata (name, model, OS)

Pult resolves the user email against existing Pult users to build device-to-user associations.

Devices are synced regardless of whether they are currently online in JumpCloud.

Pult reads the WiFi MAC address from JumpCloud System Insights. Devices without System Insights enabled are still synced and can be used for Device Authentication auto-matching via serial number, but they will not participate in WiFi Presence matching.

Capabilities

1. Device Authentication auto-matching

When a device initiates an authentication request, Pult can automatically identify the user:

Serial number → email → Pult user

Pult looks up the device's serial number in the synced MDM inventory, finds the assigned user's email, and matches it to a Pult user. This enables automatic device authentication for managed devices without requiring manual approval.

2. WiFi Presence

Pult uses the device's WiFi MAC address from MDM to associate observed WiFi activity with users:

WiFi MAC address → email → Pult user

When a connected WiFi client is detected, Pult matches the client's MAC address against MDM device records. If a match is found, the activity is attributed to the corresponding user, enabling automatic office presence detection.

How sync works

  • Pult polls the JumpCloud API periodically. There are no webhooks or real-time push.
  • API credentials are validated on save: invalid credentials or missing permissions are rejected immediately.
  • If authentication fails repeatedly, the integration is automatically paused until an admin resets it from the Pult Dashboard.

Requirements

  • A JumpCloud organization, hosted in either the Global or the EU region.
  • A JumpCloud service account with the Read Only role and a Client Secret key.
  • System Insights enabled on managed devices so JumpCloud reports their WiFi MAC address.
  • Devices must have a primary user assigned in JumpCloud so Pult can identify the device owner.
  • User emails in JumpCloud must match emails in Pult for automatic user resolution.

Next steps

See the Setup Guide for step-by-step instructions on configuring the integration.

Last updated on Sep 23, 2026, 6:04 PM

On this page