> 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-troubleshooting/salto-licence-expiring-emails.md).

# Salto license expiry emails

Understand Salto Bluetooth credential trial-expiry notices and integrated-system license requirements.

New Salto systems get a **1-year free trial** of Bluetooth credentials. Salto emails 30 days before expiry (SPAINT-XXXXXX, "SALTO Mobile Users expires in 30 days").

Check via Space **Info icon → View Features → Mobile guest keys / Mobile SVN**.

* **Mobile guest keys** (Gallagher part **C866020**) are required for Gallagher Credentials with Salto, except in **Salto Native Mode from CC v9.30**, where they are not.
* **Mobile SVN** (**C866021**) is **not** required for Command Centre and should be **avoided** on integrated systems.

***

🔗 **Related**

* [Salto Bluetooth licensing troubleshooting](/knowledge-hub/products/integrations/third-party-readers/salto/salto-hardware/salto-bluetooth-licencing-troubleshooting.md). The BLE license model.


---

# 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-troubleshooting/salto-licence-expiring-emails.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.