Geofencing

Geofencing is a location-based technology that creates a virtual boundary (or “zone”) around a real-world area using GPS, Wi-Fi, cellular data, or RFID signals.

When a managed device enters or exits this boundary, predefined actions are automatically triggered — such as applying security policies, sending alerts, or restricting app access.

For example, an IT admin can configure a Geofence around an office building so that when a corporate device enters the area, Wi-Fi and VPN settings are automatically enabled, and when it leaves, access to internal apps is restricted.

Key Benefits of Using Geofencing

Using geofencing in endpoint or mobile device management provides several operational and security advantages:

  • Enhanced Security: Automatically restrict access to corporate resources when a device leaves a secure location.

  • Automated Policy Enforcement: Apply or remove configurations (Wi-Fi, VPN, app access) based on device location.

  • Real-Time Visibility: Monitor the location of managed devices to ensure compliance and prevent misuse.

  • Loss Prevention: Receive alerts if devices move out of designated areas (useful for schools, logistics, or healthcare).

  • Improved Productivity: Enable context-aware settings such as silencing notifications in office zones or activating tracking for field employees.

Operational Efficiency: Reduce manual effort by automating repetitive location-based management tasks.

Prerequisites

Firebase setup is required to communicate with apps.
Firebase Setup for Android or IOS project
1. Create a Firebase project

  1. Go to Firebase Console and create a new project. [https://console.firebase.google.com]

  2. Add Android app to the Firebase project → provide package name.

  3. Download google-services.json and place it in app/ directory.

  4. Add Firebase SDK dependencies in build.gradle (project & app level).

  5. Apply Google Services plugin in app-level build.gradle.

  6. Sync Gradle to complete setup.

  7. Verify by running the app and checking Firebase connectivity.

2. Set up the project

  1. Name the Project: Define the project name.

  2. Configure Analytics: Choose to enable or disable Firebase analytics.

  3. Select Country: Specify the required country based on project needs.

To register the Android application, click the Android icon. A prompt will appear with information and options to complete the app registration.

Configuration Setup

  1. Enter the package name for the application you wish to register.

  2. Download the configuration file. This file contains the following critical parameters:

    • firebaseApiKey

    • firebaseAppId

    • firebaseProjectId

  3. Share these parameters with the Administrator. They will be passed to the application along with the MDM (Mobile Device Management) configuration.

If your iOS or Android application is already registered, the necessary configuration files, GoogleServices.json and GoogleServices-info.plist, can be downloaded. These files are located on the General Page. Scroll down on that page to view a list of all registered applications.

IOS Registration page

Android registration page

Understanding Zones

What is a Zone in WebUI

A Zone in the BigFix MCM WebUI is a logical boundary used to organize and manage devices within your environment. It allows administrators to define regions such as office buildings, restricted areas.

Zones help simplify device management and policy targeting by defining where and how configurations are applied. Each zone is associated with multiple settings.

Key Uses of Zones

  • Location-based management: Apply region-specific policies (for example, Wi-Fi or compliance rules for a particular office or site).

  • Delegated administration: Assign admins to manage devices only within their designated zone.

  • Simplified targeting: Deploy apps, certificates, or restrictions to a defined group of devices without manually selecting them each time.

  • Better visibility: View device inventory, compliance status, and health metrics filtered by zone.

Example

For instance, an organization with offices in Bangalore, Chennai, and Pune can create separate zones for each location. Administrators assigned to the “Bangalore Zone” can only view and manage devices and policies relevant to that office.