> 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/auto-assignment-card-serial-number.md).

# Configuration - Adding Auto Assignment using Card Serial Number

This procedure is split into two parts, (i.e. *Configuration in Command Centre Configuration Client*, and *Configuration in Salto ProAccess SPACE*).

**Note:** This is only supported with MIFARE Classic cards.

<details>

<summary>Configuration in Command Centre Configuration Client</summary>

1. In Command Centre Configuration Client, click **Configure** from the menu bar, then **Salto**.

   The **Salto** List Window opens.
2. **Right click** the Salto Server and select **Properties**.

   By default the **General** tab displays.
3. Click the **Cardholder Options** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-90d3ac7fbae426b0a6ce8fca620bfd27d140837f%2Fsaltoserver_cardholderoptionstab1.png?alt=media)
4. Tick the **Automatic Key Assignment** checkbox.

   This will by default enable Automatic Key Assignment for all Salto Cardholders. This can also be enabled per-cardholder via the **Salto Options** page of the Cardholder properties.
5. Select "Card Serial Number" ftom the **Key Assignment Mode** drop-down list.

   **Note:** The DESFire App Key, buttons and DESFire App ID only become enabled in "In-Memory Code" assignment mode. They otherwise are meaningless outside of this mode.
6. Click **OK** to exit and save your changes.
7. Click **Configure** from the menu bar, then **Card Types**.

   The Card Type List window displays.
8. Select your Gallagher Card Type you wish to add Salto access to, right click and select **Edit Card Layout**.

   The Card Editor window opens. This card type should already have a **Gallagher MIFARE Classic** object on it.
9. Insert a new **Salto MIFARE Classic** object.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0a467fda0ac3e014414dabf2dab7c53cdd3325da%2Fsaltomifareclassic_csn.png?alt=media)
10. Click **OK** to exit and save your changes.

</details>

<details>

<summary>Configuration in Salto ProAccess SPACE</summary>

1. Open Salto ProAccess SPACE, and select **System** > **General options** > **Users**.

   The Users tab displays.
2. Tick the **Automatic key assignment enabled** checkbox.

   **Note:** There are two format options available for the identifier, (i.e. "Card Serial Number" or "In-Memory Code").
3. Click the required **CARD SERIAL NUMBER** radio button. Verify that the Key UID format is **7-byte ROM Code (SALTO Format)**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a967a0ceb0bdb61eaae1e53a64d5496886e4b15b%2Fsaltospace_autokeyassignment1.png?alt=media)
4. Click the **Save** button.

   **Note:** Make sure the SAM & Issuing options have been configured for Salto MIFARE Classic.

</details>


---

# 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/auto-assignment-card-serial-number.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.
