> 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/products/integrations/third-party-readers/salto/overview/salto-how-credentials-work.md).

# How Salto credentials work

Understand how Salto cards receive access updates and how card validity works.

The defining concept of the Salto integration: **Salto makes access decisions on the card, not the controller.** This is the key mental model.

| Gallagher                                                                                            | Salto                                                                                                   |
| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Access decision made **at the controller**                                                           | Access decision made **on the card**                                                                    |
| Controller holds a local cardholder database, synced to the server; changes apply **within seconds** | Card stores access in sectors and objects; server changes are **not** written to the card automatically |
| —                                                                                                    | Card must be presented to an **update point** to be refreshed                                           |

### Update points

Update points refresh a card's access data:

* A Salto **wired reader** that cardholders regularly present to (ideally a door they must pass through), connected to a CU5000/CU42 device.
* Later-model **wireless readers** on an **RF3 node**, configured as update points and **online** when the card is presented.
* **Gallagher Bluetooth credentials** update via the cloud connection (not instant; refreshed regularly).

### Card validity (default 7 days)

After 7 days without an update, the card is refused at Salto locks. **Accommodation Mode** can extend this to about 1 year, but Gallagher **does not recommend it**: it ignores all schedules 24/7 and Day Categories are not applied.

### Cardholders in Salto

The Salto **SHIP** integration only creates **Visitor** cardholders in Salto. They are not visible in the Salto software, only in the Salto event trail. **Do not change** the default Visitor cardholder configuration in Salto Space. It changes Gallagher behaviour and makes fault-finding harder.

![Salto Server Properties in Command Centre: Name/IP, ports 8095/8096, Normal card access 7 days, 24/7 access 30 days, and Cardholder Defaults](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e20e13c7f2b6e1d88806c7033cc1e674d0c17301%2FSECHUB-SALTO-01-server-properties.jpg?alt=media)


---

# 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/products/integrations/third-party-readers/salto/overview/salto-how-credentials-work.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.