> 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/audit-trail-collecting-door-opening-data-using-the-ppd.md).

# Audit Trail (collecting door opening data using the PPD)

### Introduction

It is possible to know who has opened a door and at what time, by performing an audit trail on the door using the Portable Programming Device (PPD). This procedure describes how to audit a door (wireless lock only).

**Note:** You can filter the audit trail data by event date/time, access point, user/operator, operation, and/or type.

### Procedure

1. Take the PPD and go to the door to be audited.
2. Turn the PPD on by pressing the 'red' key once.
3. From the PPD main menu, select the **Collect Openings** menu option.
4. Press the 'green' key to validate the choice.

   The message *"Connect to lock"* displays on the PPD.
5. Connect the PPD to the lock using the communication cable.

   Data transfer takes place.
6. Go back to the Salto server and connect the PPD to the USB port.
7. If the message *"Connect to lock"* displays on the PPD, press the 'red' key to go back one menu level.

   **Note:** If you do not do this step, you will not be able to communicate with the Salto server.
8. In the Salto application select **System > PPD**.

   The PPD information screen is displayed. The Audit Trail information screen is automatically updated with the information from the connected PPD when you display the PPD information screen.
9. Select **Monitoring > Audit Trail**.

   The Audit trail information screen, showing the new audit trail data is displayed.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-44424b8bcf3711bad9677f383715bdce54d5689a%2Faudittrail.png?alt=media)

   **Note:** Any failed opening attempts, (e.g. someone attempts to open a door they do not have access to), display in 'red'.
10. Use the remainder of the buttons as (and if) required.

    **Note:** Once these events have been uploaded to the Salto server they will be automatically synchronised in Command Centre.

    <table><thead><tr><th width="144">Button</th><th>Description</th></tr></thead><tbody><tr><td>Advanced filtering</td><td>By clicking this button you are able to filter events to find specific information.</td></tr><tr><td>Purge</td><td>It is recommended that you make audit trail purges at least once a month. When the audit trail is not too full, all the communications with the wired units are faster, (i.e. communication with the Control Units, upload and download of PPD data.</td></tr><tr><td>Print</td><td>This button allows you to have all the information in the audit trail printed on paper.</td></tr></tbody></table>


---

# 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/audit-trail-collecting-door-opening-data-using-the-ppd.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.
