> 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

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/user/guide/events-and-notifications/movement-monitoring/parking-state-detection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.