> 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-installation-instructions/6-salto-server-connection/3-enabling-salto-native-users-mode.md).

# 3. Enabling Salto-Native Users Mode

1. Click the **Calendar Options** tab.

   This tab allows you to select three special Day Categories and a Calendar which will be reflected in Salto.

   **Note:** If you have enabled Native Mode, once Day Categories and Calendars are selected in Command Centre they are reflected in Salto.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-316afb1ce669ae0e370bf9bc78283324417c30c9%2Fsaltoserver_calendaroptionstab.png?alt=media)
2. The **Special Day Categories** section allows different access times to be configured for special days so that cardholders can have different access depending on the day.

   Select the appropriate options from the **Holiday**, **Special Day 1** and **Special Day 2** drop-down lists.

   **Note:** Each drop-down list shows the available Special Day Categories and Calendars within an operator’s divisional privileges.
3. Select the appropriate 'Calendar' from the drop-down list to be used as the **Default SALTO User Calendar**.

   **Note:** If **Calendar** is not selected, the system will use the "Default Calendar" as the Salto User Calendar.
4. Click **Apply** to save your changes.
5. Once HTTPs communication is established, in Configuration Client, click the **Enable SALTO Native Users** button on the **Settings** tab of the Salto Server properties.

   **Note:** Salto Native license is required to Enable SALTO Native Users.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c6d237eda59bb86fa919198498582135dfdf5815%2Fsaltoserver_settingstab_httpsselected2.png?alt=media)

   The following prompt displays:

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

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dba2172a0d41ab0e6f5d00b0cb98f95b8b899126%2Fsaltoserver_settingstab_nativeusersenabled.png?alt=media)

   After moving to "SALTO Native Users" mode:

   * The **Enable SALTO Native Users** button is disabled and an event is generated.
   * A "GallagherCommandCentre" partition is created in Salto Space which will be used to separate Command Centre created/used items from other items in Salto. The partition protects all Command Centre used Salto Users, Access Levels, Cardholder Timetables and Calendars in Salto Space. It is important to leave this data untouched because they are managed by Command Centre. Any Salto Space operator other than the default system operator should be restricted from accessing the "GallagherCommandCentre" partition.

     How long it takes to sync cardholders and access privileges is dependant on the number of cardholders and Salto doors, (e.g. up to 10,000 cardholders can take up to 15 minutes).
   * The Salto Server status will be changed to *"SALTO Native Users"* on the **Status and Overrides** tab.

     ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1aa5c8819188b9d4ccaece2ac83b23a35be8ccd6%2Fsaltoserver_status%26overridestab.png?alt=media)

     If the site is updated from Legacy to Salto Native Users mode, then the status message will display if there are any Salto Legacy User(s) remaining, and how many.

     ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2361c6f7964a2a5f9c62bce3b84628b86f015fef%2Fsaltoserver_status%26overridestab2.png?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/configuration-client/integrated-systems/salto-lock-interface/space-installation-instructions/6-salto-server-connection/3-enabling-salto-native-users-mode.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.
