> 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/security/lockingunlocking-padlock.md). # Locking and unlocking padlock The **Locking/Unlocking padlock** rule is essential for organizations using GPS-enabled smart locks to secure valuable assets and critical areas. This rule monitors the status of these locks, ensuring that users are instantly notified whenever a lock is engaged or disengaged. Specifically designed for GPS locks, this rule provides real-time alerts for all lock interactions, whether securing an area or locking cargo in a container. ## Rule settings This rule is entirely dependent on the device's capabilities and hardware configuration. There are no specific settings to configure within the rule itself. For common settings, see [Rules and Alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * **Reset timer:** The **Locking/Unlocking padlock** alert has a 1-minute reset timer, meaning it doesn't trigger more frequently than once every minute. Events occurring during this reset period are omitted from notifications and reports. * **Multiple devices:** This rule supports multiple GPS devices, provided they can detect Locking/Unlocking (Padlock) events and have the feature integrated into the Navixy platform. Users can monitor these events across various devices efficiently. * **GPS-independent processing:** The platform processes and displays Locking/Unlocking events even if the data packet lacks valid GPS coordinates. These events are recorded regardless of whether they occur inside or outside a geofence, ensuring no critical event is missed. --- # 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/security/lockingunlocking-padlock.md?ask=&goal= ``` `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.