> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/release-notes/web/2026/release-15-44-arm-disarm-pin-audit-events.md).

# Release 15.44: Arm / Disarm PIN Audit Events

March 17, 2026

Updates to the Solink platform in this release include:

***

## Enhancements

* [Arm / Disarm PIN](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/arm-disarm-pin.md): Added [alarm audit events](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/alarm-audit-events.md) whenever an individual does one of the following:
  * Updates the PIN
    * Updating the PIN includes changing the PIN name, PIN number, or disarm period. Any of these changes leads to a new alarm audit event.
  * Deletes a PIN
  * Adds a PIN
  * Views a PIN (toggle the "hide" button to reveal the PIN number)

***

## Bug Fixes

* [Scheduled Spot Check](/docs/understand-your-business/ai-features/solink-sidekick-ai/sidekick-scheduled-spot-check.md): Fixed an issue that caused the saved start time/date to change when editing the Scheduled Spot Check.
* Scheduled Spot Check: Removed ability to change expiration options once the spot check is saved. A new Scheduled Spot Check must be created if you wish to set a new expiration date and/or number of occurrences.


---

# 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://help.solink.com/docs/release-notes/web/2026/release-15-44-arm-disarm-pin-audit-events.md?ask=<question>&goal=<user_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.