FAQ: Geofencing

Q: What is Geofencing? 

A: Geofencing uses the physical address of a Cloud Node—paired with a mobile device’s GPS location—to enforce location-based restrictions on Mobile Button credentials. This ensures that actions such as unlocking a door can occur only when the user is physically near the property.

Q: Why is PDK adding Geofencing? 

A: As Product and Engineering expanded support for MDU tenants and residential use cases, it became clear that delivering a secure and intuitive user experience—particularly around the PDK Access App and Mobile Button credentials—required location-based safeguards. 

Geofencing addresses this by enforcing location-based restrictions on Mobile Button usage. The credential only works when the user is physically near the property, enhancing security, building trust, and enabling broader adoption of mobile-based access in MDU environments.

Q: Who is the primary user of this feature? 

A: Dealer Integrators/Installers/Admins will need to set the address for the Customer or when adding a new Cloud Node. Once configured, the Site/Property Admin can apply georestrictions to Mobile Button Credentials within any Access Rule, providing powerful, flexible control over when and where those credentials can be used.

Q: What changes for Dealers during new Customer Creation? 

A: The familiar workflow of adding a customer and setting up a Cloud Node remains, but there are going to be new required fields added to capture the system’s physical location and business details. 

Required Fields: 
1. Customer Name 

2. Address (full address: street, city, state, zip, country) 

• Validated using Google Geolocation API services 
• Coordinates may also be captured via ‘Use My Location’ on a mobile device 
• This address becomes the initial Cloud Node’s enforcement location 

3. Site Industry 

• Dropdown selection
• If “Other” is selected → required text entry (200 - character limit) 

4. Install Type 

• Only visible to Dealer OU Users 
• Options: 
  • New Install 
  • Replace/Upgrade Existing System 

Fields that remain the same: 

• Credential Toggles 
• Reporting Plan selection 

*All captured information is saved and visible later in System Settings → Customer Information

Q: Why is a Cloud Node address required? 

A: Effective geo-restriction requires the system to know the exact physical location of the Cloud Node or site. This address serves as the anchor point for determining whether a user is close enough to use their Mobile Button Credential.

Q: How are addresses validated? 

A: The address validation workflow will use the Google Geolocation API to: 

• Validate Full Address 
• Prevent invalid or partial entries 
• Optionally store latitude and longitude for improved precision 

Q: What happens after the customer site is created? 

A:  Once the customer is created, the first Cloud Node added will inherit the address entered during the Customer Creation process. The Integrator can review and update these settings under: Configuration → Cloud Node Details → General Tab → Location

Q: How will Geofencing work with multiple Cloud Nodes? 

A: When a system contains multiple Cloud Nodes, each Cloud Node must have its own assigned address to support accurate geo-restrictions. The address serves as the source of truth for determining GPS coordinates and enforcing location-based controls.

How addresses are handled:

• First Cloud Node:
  • The address is automatically inherited from the Customer information entered during account creation.
  • It can be updated later in the Cloud Node configuration screen if needed.
• Additional Cloud Nodes:
  • An address becomes a required field when adding any subsequent Cloud Node.
  • If an existing Cloud Node was created without an address, the Integrator or Admin will be prompted—via the Person/Group Rule interface—to assign one before Geofencing can be enabled.

This ensures each Cloud Node has a defined physical location, allowing Geofencing to function properly across multi-node systems.

***When creating an Access Rule, all devices in the system—regardless of which Cloud Node they belong to—will be available to select. If an Access Rule includes devices that span multiple Cloud Nodes, each Cloud Node will independently enforce its own geofence based on its configured address.***

Q: How will Geofencing be enabled on existing systems? 

A: Existing systems will support Geofencing as soon as every Cloud Node on the system is running the required 2.4.x Cloud Node software. Once updated, the Dealer or Customer Admin will need to confirm that each Cloud Node has a valid, complete address configured in its General tab.

• If an address is missing, the Cloud Node will not enforce geolocation checks until one is added.
• Systems with multiple Cloud Nodes must have each Cloud Node configured with a valid address before geofencing can operate consistently across all devices.

Q: Will Mobile App users need to update their app to use Geofencing?

A: Yes. Mobile App users will need to update to the latest version of the PDK Access App to ensure their device supports location verification and geofencing logic.

Q: What happens if a user’s phone cannot obtain a GPS signal?

A: Geofencing requires the phone to provide a valid GPS location. If a user’s device cannot obtain a GPS signal—such as in underground parking, elevators, or areas with poor reception—the system cannot confirm proximity to the property, and the Mobile Button credential will not activate.

Once the device regains a location signal, the credential will function normally.

Q: How accurate is the location detection?
A: Location detection is generally accurate within a small radius around the property. 150m is the smallest fence that can be configured from the Cloud Node. PDK uses the mobile device’s GPS, which typically provides sufficient precision to determine whether a user is near the Cloud Node’s address.

Q: What happens if the Cloud Node is offline? 
A: The Mobile Button credential will not function while the Cloud Node is offline. Remote lock and unlock actions require the Cloud Node to be online to validate the location and process the request.