> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/events-and-notifications/movement-monitoring/parking-state-detection.md). # Parking state detection Receive notifications when a vehicle starts or ends a parking period. Monitor off-duty vehicle use or bind the rule to geofences to track dwell time. This rule allows users to receive notifications when a device starts or ends parking. For example, organizations that want to control the driving time of their vehicles can use this rule to ensure vehicles aren’t used off-duty. This rule provides notifications to the user interface, email address, or phone number about the parking states of selected objects. Setting up this rule helps users stay informed about the beginning and end of trips, as well as changes in the parking status of their vehicles. This enhances control, security, and efficiency in fleet management operations. ## Rule settings **Parking detection configurations** The settings for a parking detection rule are managed exclusively within the Parking Detection widget. For detailed information on configuring parking detection, see the Parking Detection article. For common settings, see [Rules and Alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * The "Parking state detection" alert has a 10-second reset timer, which means the alert event won't occur more often than once every 10 seconds. If an event occurs while the rule is waiting for the reset, the Navixy platform omits the event, including in reports. * This rule is detected on the server side and isn't tied to any specific hardware, allowing it to be applied to multiple GPS devices simultaneously. This flexibility enables you to manage several GPS devices within a single rule. --- # 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://navixy.com/docs/user/guide/events-and-notifications/movement-monitoring/parking-state-detection.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.