Presence Locations

Understand presence locations, public and local subnets, and how Pult matches devices to offices.

A presence location represents a physical place -- typically an office building or campus -- where Pult tracks employee attendance. Each presence location is configured with IP subnets that identify its network.

Creating a Presence Location

Navigate to Settings → Presence → Locations in the Pult Dashboard. Each location has:

Field	Description
Name	A human-readable name (e.g., "Hamburg HQ", "Berlin Office"). Shown in insights and notifications.
Emoji	An optional icon for quick visual identification.
Description	An optional description for internal reference.
Public Subnets	The WAN IP ranges that identify this location's network from the outside (up to 10).
Local Subnets	The LAN IP ranges used to disambiguate when multiple locations share a public IP (up to 10).

Public vs Local Subnets

Public Subnets

A public subnet is the external (WAN) IP range of the office location -- the IP address that devices at that location appear to come from when connecting to the internet.

Used as the primary matching criterion for both the Pult Agent and WiFi Presence.
Most offices have a static public IP or a small range (e.g., 203.0.113.0/24).
You can enter a single IP address (e.g., 203.0.113.5) or a CIDR subnet (e.g., 203.0.113.0/24).

Offices typically use a static public IP address. If your office has a dynamic IP, contact your internet provider to request a static one. Pult cannot reliably match presence with a changing public IP.

Local Subnets

A local subnet is an internal (LAN) IP range within the office network. Local subnets are only needed when multiple presence locations share the same public IP -- for example, two office floors behind the same internet connection but on different VLANs.

Used as a secondary matching criterion to disambiguate between locations.
Only relevant for Pult Agent detection (the agent reports local IPs alongside the public IP).
If each location has a unique public IP, you do not need to configure local subnets.

How Matching Works

Pult checks the device's public IP against all configured public subnets across all locations.
If exactly one location matches and has no local subnets configured, the device is recorded at that location.
If multiple locations match the same public subnet, Pult checks the device's local IP addresses against each location's local subnets to find the correct one.

Linking to Pult Offices

Presence locations can be linked to Pult Workplace offices to enable booking automations. When a presence location is linked to an office:

Desk bookings at that office can be automatically confirmed when the employee is detected at the linked presence location.
Employees detected at the location but without a booking can receive notifications.

This link is configured in the office settings within Pult Workplace.

Multiple Locations

You can configure as many presence locations as needed. Common setups include:

One location per office building -- Each building has its own public IP and presence location.
One location per floor or wing -- Useful when different areas of the same building have separate network segments (VLANs) and you want floor-level insights.
Locations across cities or countries -- Each office site gets its own presence location with its own IP configuration.

All configured locations appear in the Presence Dashboard, and users are automatically matched to the correct one based on their network connection.