---
title: "NX Witness"
source: /gcxone/devices/nx-witness-configuration
locale: en
updated: 2026-09-17
---
## **Introduction**

This guide describes the steps required to configure NX Witness for integration with GCXONE.

## **NX Witness Configuration**

### Connecting and creating an integration user

**Step 1:** Open the NX Witness client and click **Connect to Server**. Enter the admin/owner credentials — IP address (Host), username (Login), and Password — into the popup window, then click **OK**.

![](/api/media/file/e066466eab5ac0a4112dcbdded17dfaa9b49d2ea-1920x1003.png)

**Step 2:** After logging in, right-click **Users** and select **New User...**

![](/api/media/file/7da5fd8eb9a3a54979a2224ef4725d6a97ecba1b-1920x1080.png)

**Step 3:** Fill in the new user form. **User Type** must be **Local** and **Role** must be **Administrator**.

![](/api/media/file/7cbd9fd495d854dedf712e6a62ed6377131f7f74-1920x1080.png)

**Step 4:** Make sure the **Enable** toggle is on. Click the three dots (⋯) to reveal **Allow digest authentication for this user**, and make sure it's selected.

![](/api/media/file/73b042c610544e5df76a835cde82322901e2c9c7-1920x1080.png)

**Step 5:** Once all the information is entered, the form should look like the screen below. Click **OK** to create the user.

![](/api/media/file/83a170f9f99cb814d14cc898d5ef15bdd7700c42-1920x1080.png)

### Configuring the I/O module and event rules

**Step 6:** Right-click the I/O device and select **I/O Module Issues** to configure it.

![](/api/media/file/65d49615c9d89d2a78b51a445923162f366c4849-1920x1080.png)

**Step 7:** Click **Add** to open the Event Rules window, where you'll create the rules below.

![The Event Rules window in the Nx Witness client with a rule's event list open on Device Disconnected, and the Add button arrowed at the top.](/api/media/file/11a358a5cc91542d6199b8ce3fcecfe44f371683-1920x1080.png)

**Step 8:** To add cameras or sensors as a rule's source, right-click each one individually and click **Add**.

![](/api/media/file/e0359829da4b13d4d4022db25a1f1dd672ac3f00-1920x1080.png)

**Step 9:** Create the following four rules, one at a time, using the **When** dropdown under **Event** to select each trigger:

- **Rule 1 — Device Disconnected**

![](/api/media/file/6c084be9cbb96e58ddf2028cdaa226a17ba64b14-1188x773.png)

- **Rule 2 — On Analytics Event start**

![](/api/media/file/8cdec7d830ce4e4c902260a65d5c5aa8284fc319-1188x773.png)

- **Rule 3 — While Analytics Event**

![](/api/media/file/d1da6bea3cbb4b14df47f9f198ada9d1ce4c2bea-1182x768.png)

- **Rule 4 — On Event Disconnected**

![](/api/media/file/c56dc5388f153c94bcd0ced7e338d1024bf251ca-1179x772.png)

For each rule, configure the **Action** tab to forward the event to GCXONE:

**Rule 1 (Device Disconnected) — Action tab:**

- Select: Do HTTP(S) request
- HTTP(S) URL: [https://hanwahproxy.nxgen.cloud/eventIngest](https://hanwahproxy.nxgen.cloud/eventIngest)
- HTTP(S) Content: {"eventType": "motion.novideo", "cameraid": "\[ENTER THE UNIQUE CAMERA ID\]"}
- Content Type: application/json
- Login: \[ENTER THE UNIQUE DEVICE ID\]
- Password: \[ENTER THE UNIQUE DEVICE ID\]
- Authentication Type: Basic
- Request Method: POST
- Click **Apply** and **OK**.

![](/api/media/file/817f1968fba8f2d98d3643f84150ea523c0e65b1-1182x770.png)

**Rule 2 (On Analytics Event start) — Action tab:**

- Select: Do HTTP(S) request
- HTTP(S) URL: [https://hanwahproxy.nxgen.cloud/eventIngest](https://hanwahproxy.nxgen.cloud/eventIngest)
- HTTP(S) Content: {"eventType": "analytics.intrusion", "cameraid": "\[ENTER THE NX WITNESS CAMERA ID\]"}
- Content Type: application/json
- Login: \[ENTER THE GCXONE DEVICE ID\]
- Password: \[ENTER THE GCXONE DEVICE ID\]
- Authentication Type: Basic
- Request Method: POST
- Click **Apply** and **OK**.

![](/api/media/file/91a86932204bbde68d1367cfea2f08e8113b28c2-1181x770.png)

The Login/Password and Content fields both take the GCXONE device's identifiers — for reference, an example device/sensor overview page URL in GCXONE looks like:

[https://gcx.nxgen.cloud/configuration/sp/4xxxxxxxx0eb86b5748327b437a5/customer/xxxxxxxxxa671e8539734d781/site/xxxxxxxxef44428d8574b21c1686c71c/device-group/undefined/device/de78ee2cba8a4e2c91ce887cxxxxxx/sensor/882e8f525a50444c98619e7xxxxxxxx?tab=overview](https://gcx.nxgen.cloud/configuration/sp/4xxxxxxxx0eb86b5748327b437a5/customer/xxxxxxxxxa671e8539734d781/site/xxxxxxxxef44428d8574b21c1686c71c/device-group/undefined/device/de78ee2cba8a4e2c91ce887cxxxxxx/sensor/882e8f525a50444c98619e7xxxxxxxx?tab=overview) — where **sensor id** is `882e8f525a50444c98619e7xxxxxxxx` and **device id** is `de78ee2cba8a4e2c91ce887cxxxxxx`.

![](/api/media/file/caf75254e8b7a9f021d445fcb92a184778e91ffd-1691x241.png)

Once all four rules are created, the Event Rules list should look like this:

![The Event Rules window in the Nx Witness client, listing rules for device disconnection and analytics events with their sources, actions, targets and intervals.](/api/media/file/2647519a3e82eb528b96e2931ccfe0583377e544-1183x771.png)

## **NX Witness Config Guide with GCXONE**

**Step 1:** Navigate to the **Devices** tab.

![](/api/media/file/17e011c0b2c10c68d5e528288170a0a2793b33b0-1920x989.png)

**Step 2:** Click the **Add New** button.

![](/api/media/file/073e8f2d8132a7fbd3d8f2f50d3e72e3d1fb98b1-1914x991.png)

**Step 3:** The **Add Device** dialog will be displayed.

![](/api/media/file/0320f853832415bef380fce5b5f1d289f0008d1f-1920x986.png)

**Step 4:** Open the **Device** dropdown, search for **NX Witness**, and select it.

The **Connection Settings** section includes an **Enable Cloud** option, letting the same NX Witness deployment connect either through Nx Cloud or over the local network.

### Local Connection

When **Enable Cloud** is left unchecked, the device connects using the standard local network configuration. The following details are required:

- IP Address or Host Name
- User Name
- Password
- RTSP Port

![Add Device dialog for NxWitness with Enable Cloud unchecked, showing the Local Connection fields.](/api/media/file/Screenshot-2026-09-17-154112-edited-ccb6c243.png?prefix=media)

### Cloud Connection

When **Enable Cloud** is checked, the device is configured and accessed through **Nx Cloud** instead, and a public IP address or port is not required. The following details are required:

- User Name
- Password
- Server ID

A Cloud user can be added to the existing NX Witness system, and the corresponding **Server ID** can be shared with the authorized user to provide access through Nx Cloud.

![Add Device dialog for NxWitness with Enable Cloud checked, showing the Cloud Connection fields including Server ID and Portal URL.](/api/media/file/Screenshot-2026-09-17-160604-edited-74f3fa2a.png?prefix=media)

### User Benefit

This provides the flexibility to connect to the same NX Witness deployment using either Cloud-based or local network connectivity, without changing the existing deployment:

- **Cloud Mode:** Connect using a User Name, Password, and Server ID, without requiring a public IP address or port.
- **Local Mode:** Connect directly using an IP Address or Host Name, Port, and local user credentials.