> 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/schlage-lock-interface/assigning-devices/assigning-schlage-pims-panel-interface-modules-to-a-gallagher-controller.md).

# Assigning Schlage PIM's (Panel Interface Modules) to a Gallagher Controller

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#tree-view)).
2. Highlight the Controller you want to assign the Schlage PIM to.

   **Note:** The Gallagher Controller should already be configured for Schlage devices. See [Configuring a Gallagher Controller for Schlage RS485 Devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/configuring-a-gallagher-controller-for-schlage-rs485-devices.md) for the procedure.
3. **Right click** and select **Properties.**

   By default the **General** tab displays.
4. Click the **Schlage PIMs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-29ad3386228279cb7958469249ccc9abb77fa86d%2Fschlage_controller6000pims2_tab.png?alt=media)
5. From the **Hardware** List Window, select the Schlage PIMs attached to this Bus. Drag and drop each Schlage PIM into the grid on the **Schlage PIMs** tab.

   Each of the columns, (i.e. **RS-485 Address**, **Low Door** and **High Door** ) are populated according to configuration on the **Setup** tab of the Schlage PIM.
6. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/schlage-lock-interface/assigning-devices/assigning-schlage-pims-panel-interface-modules-to-a-gallagher-controller.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.
