> 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/cloud-services/onelink.md).

# OneLink

Configure OneLink cloud-assisted controller connectivity and addressing.

OneLink lets a remote Controller 7000 connect to a cloud-connected Command Centre over the internet, with no site-to-server WAN or VPN required. The controller dials out to the Gallagher Cloud on port 443, then communicates through the cloud to the Command Centre server.

OneLink is an environment allowing remote C7000 controllers to connect to a cloud-connected system (from version **9.30.1594**) through an internet connection.

* The controller connects to the Gallagher Cloud through **port 443**.
* Once connected, it continues to communicate **through the cloud** to the cloud-connected Command Centre server.
* If a site has multiple OneLink controllers on the **same local network**, they can talk to one another on **port 1072**, but still talk to the server through the cloud.

> 🧭 **Where to start**
>
> * **Planning a deployment?** Read the requirements below.
> * **How does the traffic flow?** → [Communication](/knowledge-hub/products/cloud-services/onelink/communication.md)
> * **Setting one up?** → [Configuration](/knowledge-hub/products/cloud-services/onelink/configuration.md)
> * **What can and can't it do?** → [Limitations and Licensing](/knowledge-hub/products/cloud-services/onelink/limitations-and-licensing.md)

## Requirements

> **Important - CEIP prerequisite:** before deploying a C7000 via OneLink on a **production** licence, register the site in the **Customer Experience Improvement Program (CEIP)**:
>
> 1. Open Command Centre (9.30+).
> 2. Click the three-dot menu (top-right).
> 3. Select **"Product Alerts and Customer Experience Improvement Program"**.
> 4. The customer completes the CEIP registration form.

| Requirement             | Detail                                                                       |
| ----------------------- | ---------------------------------------------------------------------------- |
| Command Centre version  | **9.30.1594+**                                                               |
| Controller model        | C7000 **SD, Standard, Enhanced or High Sec**. **No C6000 support planned.**  |
| Controller internet     | Must reach the internet (local network or cellular modem)                    |
| Server cloud connection | CC server connected to the Gallagher Cloud (**TCP 443**)                     |
| Controller firmware     | **9.30.360** firmware **before** configuration (package **vCR930.250422b+**) |


---

# 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/cloud-services/onelink.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.