> 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/products/integrations/third-party-readers/salto/salto-reference-and-faqs/salto-an-introduction-to-licencing.md).

# Salto licensing

Reference the Salto licenses needed for integration and their hardware requirements.

Two licences make Salto work:

1. **Command Centre licence.** `CommandCentre.lic` sets the number of configurable SALTO doors (`Salto Doors = x`), bought individually or with a lock from Gallagher.
2. **Spaint licence.** Allocated on first Salto purchase through Gallagher, loaded into Salto's software, and **unique to each site**.

Both are obtained via the **Sales Support Team**.

{% hint style="warning" %}
The Spaint number must be issued by Gallagher. Numbers acquired elsewhere cause syncing and encoding failures. Online-purchased SPAONLINE/SPABASIC licenses must be upgraded to SPAINT-3XXXXX (contact Salto Tech Support or Customer Service with the serial).
{% endhint %}

The integration licence depends on the hardware source: **2A8996** (integration *without* hardware, bought elsewhere) or **2A8953** (integration *with* Gallagher hardware). The **SOM** verifies the PO.


---

# 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/products/integrations/third-party-readers/salto/salto-reference-and-faqs/salto-an-introduction-to-licencing.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.