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

# Audit Events

[Updated in 2026.23](https://docs-classic.cognigy.com/release-notes/2026.23.md)

The *Audit Events* interface allows users with the `admin` and `fullUserSupport` roles to track events at an organization-wide level. For installations integrated with NiCE CXone, this interface also tracks user, tenant, and role sync events triggered by the integration. You can also track events related to this integration in the [Activity Audit Report](https://help.nicecxone.com/content/dashboardwem/activityaudit.htm) in NiCE CXone.

You can access the **Audit Events** page using one of the following options:

* Click **User Menu > Admin Center** on the **Main** page, then select **Audit Events** from the left-side menu.
* Select **Admin Center** from the User Menu in the bottom-left corner of the **Project** page, then select **Audit Events** from the left-side menu.

## Working with the Audit Events Interface

> [accordion] View List of Audit Events
>
> The list of audit events displays all events that occurred in the past 30 days. You can filter and sort the events.
>
> | Column Name | Description |
> | - | - |
> | Type | The category of the event, such as `Action`, `Create`, `Replace`, `Patch`, `Delete`, `Authorization`, or `Authentication`. |
> | Action | The specific action that triggered the event, such as `cancelTask`, `addRoleToUser`, or `addProjectMember`. |
> | Resource Type | The type of resource involved in the event, such as Project, Node, Flow, and others. |
> | Timestamp | The exact date and time when the event occurred. |
> | Project | The identification number of the Project where the event occurred. |
> | User Email | The email address of the user who triggered the event, identifying the responsible party. |

> [accordion] View User Details
>
> To view the details of the user who initiated the audit event, follow these steps:
>
> 1. Access the **Audit Events** page using one of the following options:
>    * Click **User Menu > Admin Center** on the **Main** page, then select **Audit Events** from the left-side menu.
>    * Select **Admin Center** from the User Menu in the bottom-left corner of the **Project** page, then select **Audit Events** from the left-side menu.
> 2. On the **Audit Events** page, click the user's email in the audit event row. The system will open a window showing the user's Projects and roles within the organization.

> [accordion] View Event Chain
>
> To view an event chain, follow these steps:
>
> 1. Access the **Audit Events** page using one of the following options:
>    * Click **User Menu > Admin Center** on the **Main** page, then select **Audit Events** from the left-side menu.
>    * Select **Admin Center** from the User Menu in the bottom-left corner of the **Project** page, then select **Audit Events** from the left-side menu.
> 2. On the **Audit Events** page, hover your cursor over an audit event row to view the event's chain. The system will display the dependencies of all resources related to the event. For example, for the Node resource type, the dependencies will appear in the following format:
>
>    ```txt theme={null}
>    locale 67291073e1a6d2732253b620
>      → flow 6732fb2eb23a1561e0c4a91b
>         → node 6732fc9903cb134f00e349ad
>    ```

> [accordion] View Audit Event Details
>
> To view audit event details, follow these steps:
>
> 1. Access the **Audit Events** page using one of the following options:
>    * Click **User Menu > Admin Center** on the **Main** page, then select **Audit Events** from the left-side menu.
>    * Select **Admin Center** from the User Menu in the bottom-left corner of the **Project** page, then select **Audit Events** from the left-side menu.
> 2. On the **Audit Events** page, select an event from the list. The **Raw Event Details** window appears on the right side of the page.
>
> The event is displayed in JSON format. You can copy the event data by clicking ![menu](https://mintcdn.com/cognigy-docs-legacy/eGdkyf6N-EPpPKZA/_assets/icons/black-and-white/vertical-ellipsis.svg?fit=max\&auto=format\&n=eGdkyf6N-EPpPKZA\&q=85\&s=a0950206071f605a344eb960ca6dbfee) **> Copy Event Details**.
>
> To learn what the JSON contains, see [View Raw Event Details](#view-raw-event-details).

> [accordion] View Raw Event Details
>
> The **Raw Event Details** panel shows the event in JSON format. The following example shows an update to a Playbook step assertion:
>
> ```json theme={null}
> {
>   "_id": "6af1700ef0dbb38b0c773701",
>   "timestamp": "2026-11-09T07:02:37.000Z",
>   "type": "patch",
>   "user": "user@example.com",
>   "userReference": "63ca7c200d733eefd7512500",
>   "organisationReference": "63babf6e92add771923e8700",
>   "chain": [
>     { "elementId": "69b00b42fbaebf2952cb4000", "elementType": "playbook" },
>     { "elementId": "69b00b42fbaebf2952cb4001", "elementType": "playbookStep" },
>     { "elementId": "69b00b42fbaebf2952cb4002", "elementType": "playbookStepAssert" }
>   ],
>   "payload": {
>     "params": { "text": "Hi! What language do you prefer??" }
>   },
>   "changes": [
>     {
>       "field": "text",
>       "oldValue": "Hi! What language do you prefer?",
>       "newValue": "Hi! What language do you prefer??"
>     }
>   ],
>   "expiresAt": "2026-12-09T07:02:37.000Z",
>   "projectReference": "65ae8e3adc2d77e6e260aa00"
> }
> ```
>
> **Previous and new values**
>
> For some update events, the JSON includes a `changes` array with the previous and new values of each changed parameter. The array is available for updates to these resources:
>
> | Resource | Fields listed | Notes |
> | - | - | - |
> | Playbook step assertions (`playbookStepAssert`) | The changed parameters | - |
> | Lexicon keyphrases (`lexiconKeyphrase`) | `value` | - |
> | Knowledge Sources (`knowledgeSource`) | `name`, `description`, `status`, `metaData.*`, `data.*` | - |
>
> The event lists only parameters whose values changed. If nothing changed, for example, when you save an assertion without editing it, the event has no `changes` key.
>
> Each entry in `changes` contains the following fields:
>
> | Field | Description |
> | - | - |
> | `field` | Name of the changed parameter, for example `text` or `fuzzy`. |
> | `oldValue` | Value before the change. Missing if the parameter didn't exist. |
> | `newValue` | Value after the change. |
>
> **Omitted values**
>
> For parameters with credential-like names, such as `apiToken`, and for values that contain secret keys, such as `password`, the event lists the field name only. This also applies to `metaData.url` of Knowledge Sources, because a URL can contain a signature or credentials.

## More Information

* [Admin Center Dashboard](https://docs-classic.cognigy.com/ai/administer/access/admin-center/dashboard.md)
* [Admin Center](https://docs-classic.cognigy.com/ai/administer/access/admin-center/overview)
* [Access Control](https://docs-classic.cognigy.com/ai/administer/access/admin-center/access-control.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.