> 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-site-configuration/salto-rooms.md).

# Salto Rooms

### Introduction

This procedure describes how to create the access control for Rooms (wired online, non-wired offline and wireless locks) within the Salto application.

Rooms are used for hotel guests only. These access points are then made visible to hotel check in operators within the Salto application.

**Note:** Salto Rooms are represented as Salto Door items in Command Centre.

### Procedure

1. Select **Access points > Rooms**.

   The Rooms screen is displayed.
2. Click **Add Room**.

   The Room information screen is displayed.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3ab44a32183ba66126268f8fd9d9e7d0a8f6075b%2Froom.png?alt=media)
3. Type a name for the Room in the **Name** field.

   **Notes:**

   * The Room naming convention must be the same as that used in the hotel PMS system.
   * Rooms are represented as Salto Door items in Command Centre, so it is recommended that you clearly identify this item, (e.g. #808 - Room 8, Floor 8). Characters '@' and '(X)' should not be used in the name field.
   * The Salto Room name must match the Command Centre name. If the names do not match, card events will not show the source and the next 'Update Access Points' will cause the Command Centre item to be deleted.
4. Type a description for the Room in the **Description** field.

   **Note:** If a description is entered, it will not be replicated to Command Centre during an 'Update Access Points'.
5. Select the appropriate configuration options.

   **Note:** The default opening mode for Rooms and Suites is Standard. However, you can change this to Toggle mode in the General options if required. To do so, select the **Toggle** option from the **Open mode** drop-down list in **System > General options > Hotel**. The selected opening mode applies to all external room doors in the hotel. However, it does not apply to doors in sub-suites.

   <table><thead><tr><th width="174">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Connection type</td><td>This drop-down provides a list of connection types for the room. The default option is Offline. When you select any other (wireless) connection types from the <strong>Connection Type</strong> drop-down list, a <strong>Configure</strong> button is displayed on the Room information screen. Additional panels are also displayed on the Room information screen, depending on the connection type selected. Connection types are: Offline, Online IP (CU5000), Online IP (CU4200), Online RFnet, Online BLUEnet and Online BAS.</td></tr><tr><td>Audit on keys</td><td><p>Allows monitoring of when and where keys are used. You must enable this feature on both the access point and the user’s key. When this option is selected, the door is enabled to write or stamp the audit on the key as long as the key’s memory is not full.</p><p><strong>Salto Default</strong> = Off (should be changed to ON for non-wired offline locks)</p><p><strong>Command Centre Equivalent</strong> = Automatic in Command Centre.</p></td></tr><tr><td>Audit inside handle opening</td><td>Allows monitoring of when a guest exits a room. For RF doors, this data is automatically transferred and displayed in the audit trail.</td></tr><tr><td>Allow mobile check-in</td><td>Allows mobile guest keys to be used to access a room. Mobile guest keys allow guests to access a room by using the JustIN key app on their mobile phone (instead of a separate physical credential). When you select this option, a <strong>Send key to guest’s mobile</strong> checkbox and a <strong>Notification message</strong> field are displayed on the Hotel check-in screen for the room. This option is currently only compatible with smartphones using iOS or Android operating systems.</td></tr><tr><td>Open time</td><td>This field determines the time passed from the moment access is granted, until the electronic system locks it again.<br><strong>Salto Default</strong> = 6<br><strong>Command Centre Equivalent</strong> = Door unlock time<br><strong>Command Centre Default</strong> = 5</td></tr><tr><td>Increased open time</td><td>Defines a longer opening time. This option is designed for disabled or ‘hands full’ guests. The default time value is 20 seconds. The value can be increased or decreased in the range 0 to 255 seconds. You must enable this option in the user’s profile. If extended access time is used in Command Centre, it is then used in Salto as the increased open time.<br><strong>Salto Default</strong> = 20<br><strong>Command Centre Equivalent</strong> = Extended access time<br><strong>Command Centre Default</strong> = 25</td></tr><tr><td>Suite</td><td>Selecting a suite from the drop-down list.</td></tr></tbody></table>
6. Click **Save**.

### What happens next?

You will now need to associate a Salto zone with the Room. Salto guest access to the Salto zone will provide access to the Room.


---

# 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-site-configuration/salto-rooms.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.
