> ## Documentation Index
> Fetch the complete documentation index at: https://docs.altoura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit Logs Generation - Connectors

> When you link two nodes in the Experience Node Editor, the audit log records an Operation of Connected Node. Expanding that log entry reveals the NodeID of the target node to which the current node was linked.

<img src="https://mintcdn.com/altoura-785c3552/FoIV9SzgFfYMUXXv/images/docs/278e48c06e965f1953ae4f110ca67e6c0cf752386a7403ed1c4ab50b76e103e5-image.png?fit=max&auto=format&n=FoIV9SzgFfYMUXXv&q=85&s=9f4a60675efa16a650898f862061fbdc" alt="" width="1217" height="231" data-path="images/docs/278e48c06e965f1953ae4f110ca67e6c0cf752386a7403ed1c4ab50b76e103e5-image.png" />

When a user selects an existing connection, adds one or more Actions in the properties pane, and clicks Save, the system:

* Creates a connector and assigns it a unique **ConnectorID**

* Logs an \*\*Operation \*\*of **Added Connector Details**

* **Modifications to** will reflect the Actions added as follows:

* 1. One Action added: the ActionName appears in the column
  2. Two Actions added: both ActionNames are listed
  3. More than two Actions: the column shows Multiple attributes

* When an Action on an existing connector is updated, the log records follow the same principle,

  1. One Action added: the ActionName appears in the column
  2. Two Actions added: both ActionNames are listed
  3. More than two Actions: the column shows Multiple attributes

On expanding the audit-log row, all details of the action can be viewed.

### Adding Connectors and Connector Actions

<img src="https://mintcdn.com/altoura-785c3552/pvN_b_9fLlPnvtUQ/images/docs/1deee20c049c9b838a5dce1c681d970255f6f05fe50d95b84bc4731ce2278784-image.png?fit=max&auto=format&n=pvN_b_9fLlPnvtUQ&q=85&s=ae16491db8102c04d76d3033adc103bc" alt="" width="1222" height="230" data-path="images/docs/1deee20c049c9b838a5dce1c681d970255f6f05fe50d95b84bc4731ce2278784-image.png" />

### Updating Connector Actions

<img src="https://mintcdn.com/altoura-785c3552/FoIV9SzgFfYMUXXv/images/docs/3598e745731ddfc84892ce85cbed07f5619d22c6634bdc9242f45342fa8f14f1-image.png?fit=max&auto=format&n=FoIV9SzgFfYMUXXv&q=85&s=d95e59bdfa176e5b5d9c16aa87ab3de7" alt="" width="1221" height="171" data-path="images/docs/3598e745731ddfc84892ce85cbed07f5619d22c6634bdc9242f45342fa8f14f1-image.png" />

### Deleting Connector Actions and Connectors

* **Individual delete entries**: Every connector action deletion appears as its own audit-log row.

* **Action Deletion vs. Connector Deletion:**

  * Removing a single connector action logs one “Deleted Connector Action” entry along with the instance name of the action.
  * If that action was the connector’s last action, the system then logs a separate “Deleted Connector” entry.

* **Link persistence**: Deleting an action does not sever the node-to-node link—only the connector itself is removed once its final action is deleted.

* **Explicit connector removal:** Choosing Delete Connector (via the Node Editor menu or the properties pane button) immediately logs 2 entries one for “Deleted Connector” and one for the Disconnected Node.

<img src="https://mintcdn.com/altoura-785c3552/RIgkSrBJFuycivOX/images/docs/fafabee1acb203708e7c121e0db657af540ec2a9ffa9fdd77b200896e7dfd25d-image.png?fit=max&auto=format&n=RIgkSrBJFuycivOX&q=85&s=3aec9b544b8e2a3583dce2163a5e588e" alt="" width="1217" height="267" data-path="images/docs/fafabee1acb203708e7c121e0db657af540ec2a9ffa9fdd77b200896e7dfd25d-image.png" />