> 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/aperio-integration/configuring-the-aperio-locks-readers/configuring-the-security-mode-encryption-between-hub-and-lock.md).

# Configuring the Security Mode (Encryption between hub and lock)

Aperio locks support two security modes - Manufacturer mode and Customer mode.

In customer mode, the lock uses secure radio communication with the customer encryption key. Whereas in manufacture mode, the lock uses insecure radio communication with the default encryption key. The default mode is Manufacture mode. Both the hub and the locks/readers must have same security mode configured for successful communication. The hub will not be able to communicate with the lock/reader if the security mode is different.

It is always **recommended to switch to customer mode** but only after the Aperio locks have been paired and configured.

**Gallagher recommends the following sequence for switching the locks to customer mode:**

1. Pair the locks/readers with communication hub.
2. Configure the communication hubs.
3. Configure the locks/readers.
4. Add the Aperio locks/readers in Command Centre and bring them online.
5. Switch to customer mode on the locks/readers.
6. Switch to customer mode on the hub.

If is not recommended to change the configuration on locks or hubs in customer mode. Always switch back to manufacture mode (locks first and then the hub) before making any configuration changes.

**Important:**

* Never unpair the locks when in customer mode. Always switch to manufacture mode first. If a lock is unpaired in customer mode, it might not be able to use the pair the lock with any other hub unless it’s a version 3 lock with USB connection.

  V3 locks with USB can be connected to PAP and configured.
* It is very important to take care of the sequence when changing the security mode. All the locks paired with the hub must be switched to customer mode before switching to customer mode on the hub. Similarly, all the locks paired with the hub must be switched to manufacture mode before changing the mode to manufacture mode on the hub.
* The encryption key used when in customer mode is the same key used when creating an installation in PAP s/w. It is important to keep the key safe and never lose it.

<details>

<summary>Procedure to switch to customer mode</summary>

#### Change security mode on the lock first

1. In the Aperio Programming Application, **right-click** on the lock to be configured and select **Lock/Sensor** > **Switch to Customer Mode**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d17cb5132539e3bf4ff5836f7c3e3909ca1af39a%2Fsecuritymode_1.png?alt=media)
2. Follow the on-screen instructions to show card or engage sensor when required.
3. Once the security mode is changed on the lock, it will show conflict as the hub is still in manufacturer mode.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e24c2d248a8842fd8e6d0eafa7c7d5d4471be578%2Fsecuritymode_2.png?alt=media)
4. Change the security mode to customer mode on all the locks paired with the hub before proceeding further.
5. Change security mode on the hub.
6. **Right-click** on the hub and select **Switch to Customer Mode**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b93393f4a7d4be6c3f703bd5c3ef7103f2e82dac%2Fsecuritymode_3.png?alt=media)
7. Once the mode is changed on both the hub and the locks/readers, the security conflict will be resolved.

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

</details>

<details>

<summary>Procedure to switch to manufacturer mode</summary>

#### Change security mode on the lock first

1. In the Aperio Programming Application, **right-click** on the lock to be configured and select **Lock/Sensor** > **Switch to Manufacturer Mode**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2e0861837d84e0c14b995c3931489fd9bdb329f9%2Fsecuritymode_5.png?alt=media)
2. Follow the on-screen instructions to show card or engage sensor when required.
3. Change the security mode to manufacturer mode on all the locks paired with the hub before proceeding further.
4. Change security mode on the hub.
5. **Right-click** on the hub and select **Switch to Manufacturer Mode**.

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

   **Note:** Security mode can also be changed from the **Security Mode Setting** screen of the Configure Lock/Sensor wizard.

</details>


---

# 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/aperio-integration/configuring-the-aperio-locks-readers/configuring-the-security-mode-encryption-between-hub-and-lock.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.
