Getting Started
Requirements
System, network, and infrastructure prerequisites for Pult Presence.
Review the requirements below for your chosen detection method. If using both methods, ensure you meet the requirements for each.
General Requirements
These apply regardless of detection method:
- A Pult organization with admin access to the Pult Dashboard.
- Presence locations configured with the correct IP subnets for each office. See Presence Locations.
- Pult user accounts for each employee whose presence should be tracked. User email addresses must match across Pult and any connected systems (MDM, WiFi).
Pult Agent Requirements
Supported Platforms
| Platform | Architecture | Installer |
|---|---|---|
| macOS | Intel (x86_64) and Apple Silicon (ARM64) -- universal binary | .dmg (manual) or .pkg (MDM) |
| Windows | x86_64 and ARM64 | .msi |
| Linux | x86_64 only | .deb |
Linux support requires GTK 3 and WebKitGTK 4.1. See the installation guide for details.
Network Requirements
- Each office must have a static public IP address (or a small, stable IP range). Dynamic public IPs are not supported.
- The agent must be able to reach
gql.api.pult.comover HTTPS (port 443). - If employees use a VPN, configure split-tunnel routing to exclude Pult's beacon endpoint
(
18.96.35.116/30) so beacons originate from the office's public IP rather than the VPN tunnel.
Deployment Options
- Manual: Employees download and install the agent themselves, then sign in with their Pult account.
- Automated (MDM + Bootstrap Token): IT deploys the agent via MDM and uses a bootstrap token for hands-free enrollment. See Bootstrapping and MDM Deployment.
WiFi Presence Requirements
Supported WiFi Controllers
| Provider | Type | Notes |
|---|---|---|
| Cisco Meraki | Cloud-managed | API key authentication |
| Aruba Central | Cloud-managed | OAuth2 authentication via HP GreenLake |
| UniFi (Ubiquiti) | Self-hosted with API access | Requires port forwarding and firewall rules |
WiFi Presence requires a cloud-managed WiFi controller (or, for UniFi, a controller with API access). On-premise-only WiFi systems without an API are not supported.
Supported MDM Systems
At least one MDM integration is required for WiFi Presence to map devices to users:
| MDM Provider | Authentication |
|---|---|
| Microsoft Intune | OAuth admin consent |
| Jamf Pro | API client credentials (cloud only) |
| Kandji | API token |
| SOTI MobiControl | OAuth2 |
| Mosyle Business | API token + service account |
Alternatively, you can import devices manually via CSV if no MDM is available.
Device Requirements
- MAC address randomization must be disabled on managed devices. Private/random MAC addresses
prevent reliable matching between WiFi activity and MDM device records.
- On Apple devices, disable "Private Wi-Fi Address" via an MDM configuration profile.
- On Windows devices, disable "Random hardware addresses" via Group Policy or MDM.
- On Android devices, disable "Randomized MAC" per network via MDM policy.
Network Requirements
- The WiFi controller must be reachable by Pult over the internet (cloud-managed controllers handle this automatically; UniFi requires port forwarding).
- For UniFi specifically: allow inbound connections from Pult's IP address (
3.73.170.193) on port 8443 (or your configured port).
Dashboard & Automations
- Booking confirmation and missing booking notifications require presence locations to be linked to Pult Workplace offices.
- Meeting room auto check-in requires the Pult Rooms integration to be configured.
Last updated on Apr 8, 2026, 11:52 PM