> 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/video-management-systems/nx-witness-vms-integration.md).

# Nx Witness VMS Integration

The Nx Witness integration is a modern camera-tile style integration, with the same feature pattern as Hanwha: tiles, up to 16 per Viewer, event-triggered display, PTZ, preset, capture frame, **4K via H.265**, and a **signed certificate required**.

Stored video is stored by the Nx Witness VMS and retrieved into the Command Centre VMS UI (alarm-associated plus pre-alarm and post-alarm, scrub, speed, toggle live and stored, and Spot Monitor Viewer).

* **Command Centre to Nx Witness:** an event or alarm can move a camera to a preset or retrieve stored video.
* **Nx Witness to Command Centre:** all Nx Witness events (including motion and diagnostics) are mappable; common ones are mapped by default

{% hint style="info" %}
Gallagher tests each integration with a small selection of cameras and can only guarantee those.
{% endhint %}

***

🔗 **Related**

* [Hanwha Vision VMS Integration](/knowledge-hub/products/integrations/video-management-systems/hanwha-vision-vms-integration.md). The same modern camera-tile style.


---

# 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/video-management-systems/nx-witness-vms-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.