> 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/command-centre-site-configuration/salto-key-assignment.md).

# Salto Key Assignment

### Introduction

The Salto Key Assignment feature allows Salto cards to be automatically encoded when presented at a wired Salto update point. This streamlines credential management for sites using Salto Space integration with Gallagher Command Centre.

This option is useful in university installations, for example, where thousands of new users (students) arrive at the start of each academic year. The automatic key assignment functionality means that users do not have to wait in line to have their key encoded. Instead, their key is assigned automatically when it is presented to a Salto update point.

Operators require the "Manage Keys" operator privilege to set up Salto Key Assignment.

**Notes:**

* The Automatic Key Assignment options do not appear for Legacy mode.
* Only wired readers can be used, (e.g. UBox400, CU4000s).
* "In-Memory Code" is for Salto DESFire cards only, (i.e. EV1 4K, EV2 4K, EV3 4K and EV3 8K), and "Card Serial Number (CSN)" is for Salto MIFARE Classic cards only.
* MIFARE Classic 1K cards are not supported as they may run out of space with multiple Card Objects. MIFARE Classic 4K cards are recommended instead.
* DESFire settings must be the same on both Command Centre systems, regardless of the fact that the Salto Server will not be online on the "Third Party" system.
* Only new cards are usable for automatic key assignment.

### Use Cases

This feature allows for two possible scenarios, as follows:

* **Adding Salto to Gallagher Cardholders**

  Sites may want to use the auto encoding feature to help migrate existing Gallagher users to having Salto access. Cardholders that benefit most would be those in remote campuses where there is no easy encoder access.
* **Pre-encoded Salto Cards**

  Sites will order Gallagher pre-encoded cards. Customers with Salto Integration will not be able to use these cards at Salto doors without going through the encoding process. Allowing pre-encoded Gallagher and Salto cards will prevent sites to encode Salto onto their cards.

  **Note:** Bureau Batch Job encoding is supported for MIFARE DESFire In-Memory Code.

### Configuration

[Configuration - Adding Auto Assignment using Card Serial Number](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/salto-key-assignment/auto-assignment-card-serial-number.md)

[Configuration - In-Memory Code Auto Assignment](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/salto-key-assignment/auto-assignment-in-memory-code.md)

### In This Section

* [Configuration - Adding Auto Assignment using Card Serial Number](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/salto-key-assignment/auto-assignment-card-serial-number.md)
* [Configuration - In-Memory Code Auto Assignment](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/salto-key-assignment/auto-assignment-in-memory-code.md)


---

# 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/command-centre-site-configuration/salto-key-assignment.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.
