> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/space-site-configuration/enable-mobile-audit-trail-for-salto-offline-doors-locks.md).

# Enable mobile audit trail for Salto offline doors/locks

### Introduction

Support for audit trails when using mobile credentials has been added in version vEL9.00 of command centre. This allows reporting of cardholder door access events via the Command Centre Cloud for Salto offline doors/locks, similar to using cards with an update point.

Audit trails will be sent from Mobile Connect to Command Centre Cloud and received by the site.

**Note:** Existing sites will need to wait until their cardholder’s Salto key expires, which is typically the next day, but may take up to the key revalidation limit that is 7 days by default, and can be configured in the "Normal Card Access" field in the **Settings** page of the Salto Server's properties.

This feature can be enabled site wide and enabled per-cardholder. The default for new installations and existing sites on upgrade is enabled.

### Prerequisites

* Gallagher Command Centre Cloud must be connected.

  Refer to [Connecting to the Cloud](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud.md) for further detail.
* Salto offline door must have "Audit on keys" enabled.

  Refer to [Salto Doors or ESDs](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/space-site-configuration/salto-doors-or-esds.md) for further detail.
* Salto Mobile Events must be enabled in Command Centre in the Salto Server item (on by default).
* Salto Mobile Events must be enabled per cardholder (on by default).

### Limitations

Similar to audit trails in cards reported via update point, cardholder events via Mobile Connect are not guaranteed to be reported. Mobile connect will attempt to retry if the cardholder has no active internet connection at the time of access.


---

# 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.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/space-site-configuration/enable-mobile-audit-trail-for-salto-offline-doors-locks.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.
