> 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-zones.md).

# Salto Zones

### Introduction

This procedure describes how to create and configure a Salto zone within the Salto application.

A zone is a specified group of access points that are grouped together to make them easier to manage in the system. For example, a zone could be the doors on the first floor, all the lockers in the gym area, or all the doors in the financial services area.

**Note:** Salto zones are represented as Salto Access Zone items in Command Centre. Changes made to Salto Zone names and descriptions in Command Centre update automatically in Salto without performing an 'Update Access Points’, when Salto is online or comes online after being offline. Likewise, Salto Zones can be deleted from Command Centre and the deletion occurs automatically in Salto when Salto is online.

### Procedure

1. Select **Access points > Zones**.

   The Zones screen is displayed.
2. Click **Add Zone**.

   The Zone information screen is displayed.

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

   **Notes:**

   * Salto zones are represented as Salto Access Zone items in Command Centre, so it is recommended that you clearly identify this item, (e.g. Level 1). Characters '@' and '(X)' should not be used in the name field.
   * The Salto zone 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 in a description for the zone in the **Description** field, if required.

   **Note:** If a description is entered, it will not be replicated to Command Centre during an 'Update Access Points'.
5. The **Low zone** checkbox should not be modified unless your locking plan needs more than 96 different zones.

   Zones are classified as 'low' or 'high' according to the way zone information is stored on escutcheons. You can create up to 96 'low' zones, and 928 'high' zones.

   Once this checkbox has been modified and changes saved, it is not possible to modify it again. From the escutcheon point of view, you can make a door belong to a maximum number of 96 'low' zones, but only 20 'high' zones.

### What happens next?

You will now need to associate Salto Doors, ESDs, Lockers, Rooms or Suites with the Salto zone. Command Centre Cardholder access to the Salto zone will provide access to the associated items. Salto guest access to the Salto zone will provide access to the associated items.


---

# 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-zones.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.
