> 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/other-salto-configuration.md).

# Other Salto Configuration

There are a number of other Salto configuration procedures that you may or may not need to perform. They are:

* Defining Calendars
* Defining Access Point Timed Periods
* Configuring Daylight Saving Time (enabled by default)
* Enabling Access Point Automatic Changes
* Defining Access Point Lock Settings
* User Card Cancellation
* Managing the Blacklist
* Automatic Audit Trail Purging
* Automatic System Auditor Purging
* Automatic Database Backups
* Defining Bluetooth settings for Gallagher Mobile Connect App

  For further detail, see [SALTO Mobile Access Integration](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/mobile-connect/salto-mobile-access-integration.md).

Refer to your *Salto ProAccess SPACE User Manual* for information about the above procedures or any additional configuration that you require.

### Forced Door and Door Open Too Long alarms

If you require Command Centre to generate 'Forced Door' and 'Door Open Too Long' alarms from Salto wired readers (Salto update point with relays), configure the following:

1. Set up a dummy door in Command Centre, with Door Lock open and Lock inputs physically connected to the door hardware.
2. The door lock relay for the Salto wired door must be connected to and defined as a push-button door release input on the dummy door.
3. The dummy door must have the door open/door locked inputs brought in via the Gallagher Controller. Therefore, the Salto wired readers need to be close enough to a Gallagher Controller to be able to bring in the door monitoring inputs.


---

# 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/other-salto-configuration.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.
