.png)
Device geofencing helps IT respond when equipment leaves an approved area, but the policy must reflect where those devices are allowed. For example, a boundary around the school works for classroom laptops that should stay on site. Laptops that students take home need a different rule, or IT will get an alert every time a student leaves with one.
Senturo lets you choose automated responses for each device group based on where the equipment is allowed to go. An email-only rule gives IT time to check whether a trip was approved before taking further action. For devices that must stay on-site, you can configure the rule to start recovery automatically.
Device geofencing compares reported location data with a virtual geographic boundary. In Senturo, a Radius geofence draws a circle around an address or map pin. A Jurisdiction geofence follows a broader boundary, such as a state or country.
You can request a custom geofence when property lines or district borders need a more specific shape.
Connect the boundary to a Security Policy Automation to choose whether arrivals or departures should trigger a response. The rule also determines which devices are covered, which actions run, and when it is active.
When a device crosses the boundary, the automation can run one action or several, in the order you set:
Notification isn’t automatic, so include Send Email to Administrator whenever someone needs to know the rule ran.
Review your device assignments to see which equipment must stay at school and which laptops students or staff can take home. Use those permissions when selecting devices for a campus-only rule, so IT doesn’t have to investigate alerts for trips the school has already approved.
Create a small device group for the first test and assign someone to check the notifications. Exclude equipment scheduled for approved off-site use, and review existing automations so another policy doesn’t lock a device during your test.
The devices must be enrolled, with the geofencing add-on enabled for your account.
Use an email-only response for the first test so you can check the boundary without restricting device use.
Open Automations → Create Automation and name the rule. Choose Outside Geofence, then select a saved boundary or create a Radius geofence using the + button. The minimum supported radius is 50 meters, which defines the boundary size rather than guaranteeing location accuracy.
Add Send Email to Administrator under Actions and select your test group under Devices. Set the active hours under During, remembering that each device applies the schedule in its own local time.
Review the Summary and Preview affected devices, complete the Pre-Save Checks, and select Save & Activate when ready.
Before you attach a lock or another restrictive action, test the rule with devices you can physically track. NIST recommends testing security configurations before deployment to uncover conflicts and compatibility issues. For this geofence, check that the alert appears when expected, that devices inside the boundary are left alone, and that no other setting changes the result.
Arrange with a colleague to take one test device outside the geofence while you keep a second device inside it. Choose a time when the automation is active, get approval for the trip, and keep both devices connected. You can then compare what Senturo reports with where you know the devices are. Check the timestamps too, because a position recorded before your colleague crossed the boundary won’t tell you whether the rule picked up that movement.
Location estimates always carry some margin, so check several known positions, including spots near your boundary, before you trust the rule to lock equipment automatically.
Record when the device leaves, when a fresh outside-location report appears, and when the email arrives. These observations help distinguish reporting delays from notification problems.
The live compliance indicator shows devices currently meeting the breach condition. Check the recipient’s inbox separately because the indicator does not confirm that an action completed.
A missing email doesn’t necessarily mean the boundary is wrong. First check whether the rule is active and the device has sent a recent location report.
On Windows, Microsoft’s location settings guidance explains that turning off location services blocks access through those services and can also restrict some apps’ access to Wi-Fi information.
On ChromeOS, system-only location access prevents apps and websites from receiving device location even when they have individual permission. Review the system-level setting as well as app access.
Our tracking troubleshooting guide recommends Wi-Fi rather than Ethernet for ChromeOS and Windows location reporting. Allow up to 15 minutes for new tracking data to arrive before you assume something is wrong.
An email alert gives your team time to check who has the device and whether its trip was approved. Keep that review in place when equipment can leave with permission, so an authorized trip doesn’t lock someone out.
For classroom equipment that must remain on-site, you may decide to start recovery automatically when it leaves. After testing the boundary, use the following sequence only where your policy authorizes IT to lock those devices:
Outside Geofence → Set Missing Mode → Senturo Lock → Send Email to Administrator
The person receiving geofence alerts needs a way to check whether a device was allowed off-site. Make sure they know who can confirm travel permissions and whose approval they need before investigating the device’s location.
If a missing device shows up back on campus, the location report can help you arrange collection, but it doesn't confirm your team has it. Once the device is handed in, mark it as found: open its Management tab and switch Device Status from Device Missing to Device Monitored. This ends real-time tracking.
An offline device can’t send fresh location data. Its last reported position may help an investigation, but it needs to reconnect and communicate with Senturo to send updated reports.
Geofencing uses geographic location, while IP Fencing checks network connections against approved IP ranges. Each automation has one trigger, so configure separate rules to use both.
Use IP Fencing to flag a device connecting from a network outside your approved list, and use geofencing when you need to know whether it has left a physical area.
You can select a saved geofence in multiple rules. Editing or deleting it affects every automation using that boundary, so review those dependencies first.
Open Account Settings → Data Import → Upload geofences and download the CSV template. Enter each geofence’s name, radius in meters, latitude, and longitude, then review the field mappings before importing.