> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/assa-abloy-ip-lock-integration.md).

# ASSA ABLOY IP Lock Integration

### Introduction

The integration of ASSA ABLOY's IN120 and IN220 wireless locksets into Gallagher's Command Centre access control solution extends Gallagher Command Centre access control to more doors — without the cost and disruption of traditional wiring. The ASSA ABLOY IN120 (WiFi) and IN220 (PoE) IP-enabled locks connect over the network infrastructure you already have, whether that's existing WiFi or structured LAN cabling, removing the need for dedicated door controllers, readers, and extensive cable runs.

That makes it ideal for hard-to-wire, heritage, or retrofit environments, where installation is faster, more flexible, and dramatically less expensive — while access management stays fully centralised in Command Centre. Because each lock makes access decisions locally, doors keep enforcing your access rules even if the network connection drops, so security is never dependent on constant connectivity.

Built to meet modern IT expectations, the integration uses secure, IP-based networking and enterprise-grade AES encryption, fitting cleanly into existing network and security policies rather than adding proprietary infrastructure to manage.

The result is compelling across higher education and K–12 campuses, government and public-sector facilities, large enterprise sites, and healthcare environments where reliability is critical: lower total cost of ownership, quicker deployment, and the ability to finally secure locations that were previously impractical to reach.

With centralised visibility, granular control, and enterprise-grade security over your existing network, it's a smarter, more scalable approach to modern access management. Credentials supported are Gallagher Non-diversified DESFire and various HID credentials.

\* Available in the US only.

### More information

For further detail refer to the document **"User Guide ASSA ABLOY IP Lock Integration (vn.nn).pdf"** located at: [Security File Transfers - Security Support - ASSA ABLOY IP Lock Integration - All Documents](https://gallagher203.sharepoint.com/sites/securityfiletransfers/securitysupport/forms/allitems.aspx?id=/sites/securityfiletransfers/securitysupport/security%20downloads/command%20centre%20and%20associated%20files/integrations/assa%20abloy%20ip%20lock%20integration\&viewid=c36f3467-6746-41fa-bbc3-6aac187f982f\&p=true\&ga=1)


---

# 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/command-centre-client/configuring-command-centre/configuring-licensable-features/assa-abloy-ip-lock-integration.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.
