> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/platform-user-guide-book/geofence.md). # Geofence Geofence functionality allows the creation of virtual boundaries, or geographical areas, that devices can detect when entering or exiting. These Geofences are fundamental for location-based automation and monitoring, enabling enhanced control and responsiveness across the platform. ### Geofence can be applied at different levels. * ***Geo-fence Alarm Rule*****:** Trigger alarms when devices enter or exit a predefined area. * ***Adaptive Configuration Rule*****:** Apply specific configuration changes to devices based on their location relative to a geo-fence. * **Configurations:** Used in Time-Driven Configurations to activate or deactivate settings based on geo-fence areas. * **Device Grouping:** Automatically include devices in groups based on their location within a geo-fence. * **Dashboards:** Visualize device locations and movement within geo-fenced areas using map widgets. Geofences are intuitive to create and manage, ensuring seamless integration with the platform's rules, configurations, and monitoring tools.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.g-iot.io/platform-user-guide-book/geofence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.