> 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-in-memory-code/command-centre-configuration-client.md).

# Configuration in Command Centre Configuration Client

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.
5. The **Cardholder Automatic Key Assignment** section will contain the default settings for this feature, and controls whether cardholders by default get their key identifier sent to SPACE.
6. Select "In-Memory Code" from 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 not relevant outside of this mode.
7. Configure as required:

   <table><thead><tr><th width="156">Field</th><th>Description</th></tr></thead><tbody><tr><td>DESFire App Key</td><td><p>Populate this field with a 32 character hexadecimal string. Characters accepted are only A-F and 0-9.</p><p>Clicking the <strong>Generate</strong> button automatically populates the field with a random hexadecimal string and enables the <strong>Apply</strong> button. If the <strong>Apply</strong> button is clicked now, the 32 characters are converted to 32 X's.</p><p><strong>Note:</strong> Clicking the <strong>Show</strong> button will display the key that you have entered. Clicking the <strong>Apply</strong> button changes the text back to X’s and the <strong>Show</strong> button is enabled again. An operator event is also logged.</p></td></tr><tr><td>DESFire App ID</td><td>Must be a hexidecimal value of exactly 6 characters.</td></tr></tbody></table>

   **Note:** Changing the **DESFire App Key** or the **DESFire App ID** comes up with warning message:

   *"Are you sure you want to change the automatic key assignment settings?*

   *Changing this will require reconfiguration on the SALTO server to match the new settings.*

   *Automatic key assignment may no longer work on existing cards."*
8. Click **OK** to exit and save your changes.
9. Click **Configure** from the menu bar, then **Card Types**.

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

    The Card Editor window opens.
11. Insert a new **Salto MIFARE DESFire** object.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-bb8e96345b25258cf9387a9460337db2cdced9f9%2Fsaltomifaredesfire_cardeditor.png?alt=media)
12. **Right click** on the Salto object, then click **Properties** from the drop-down menu.

    The Salto DESFire Properties dialog box displays:

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-de52e0721fb1958407ca80c3860e4bef647ef85b%2Fsalto_desfireproperties.png?alt=media)
13. Tick the **Key Assignment Encoding** checkbox.
14. Click **OK** to exit and save your changes.


---

# 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-in-memory-code/command-centre-configuration-client.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.
