Audit Log — Staff Action History in IZI CRM

Audit Log — Who Changed What in Your Club

The Audit Log is the IZI CRM section that automatically captures every staff operation: creating a promotion, updating a product, managing a shift, and hundreds of other mutations. An entry appears immediately after the operation completes — no configuration required on your end. The system intercepts all CRM mutations at the API level. Each row tells you exactly: who (staff member’s name and email), what they did (operation name), in which club (if the operation was club-scoped), when (date and time to the second), and the outcome — a green indicator for success, red for an error. End-user (visitor) actions are not recorded: the log tracks only staff actions that affect club configuration — tariffs, products, promotions, shift settings. Automated system operations are also captured; those entries show System in the User column instead of a name, so you can distinguish manual changes from background processes. The section lives in organization settings and is accessible to users with the AUDIT_LOG_READ permission. Filters by user, operation type, club, and date range let you narrow thousands of entries to a specific event in seconds, while the detail view exposes the exact JSON input of any mutation.

What Gets Logged

IZI logs all mutations performed by CRM users. An operation is recorded when three conditions are met:

• the user is authenticated with a CRM role;
• the request is a mutation (data change, not a read);
• the mutation belongs to the AuditLogOperationName enumeration — generated automatically from the GraphQL schema and updated whenever new features are added.

Examples of logged operations: creating and updating products, managing promotions and promo codes, working with tariffs, shift operations, and club configuration changes. System automated operations (no specific staff member) also appear in the log — with System shown in the User column.

Log Table Structure

The table has five columns. All column headers are clickable for sorting — a second click reverses the direction.

Column	What It Shows
Date & Time	Moment of the operation; colored left border — green (success) or red (error)
User	Staff member’s name and email; System for automated operations
Operation	Human-readable operation name, e.g. “Update Product”
Club	Club context of the operation; dash for organization-level operations
Actions	Button to open the detail view (appears on row hover when a record has details)

The table is sorted by date by default — most recent entries first. Pagination goes up to 100 records per page.

Filtering Records

The filter panel sits above the table and narrows results by four parameters:

• Period — date range (both boundaries inclusive);
• Users — multi-select one or more staff members;
• Operations — one or more operation types;
• Clubs — one or more specific clubs.

Filters combine freely: you can set a period, pick several users, and select an operation type simultaneously to find every attempt to modify a specific object within a given window.

Operation Detail View

Clicking any row (or the icon button in the Actions column) opens a modal with two tabs.

Overview Tab

A structured record card containing:

• Date & Time — exact moment of the operation;
• User — name and email (or System);
• Operation — human-readable name and technical operation identifier;
• Club — if the operation was scoped to a specific club;
• Errors — if status is ERROR, a block with error messages and the GraphQL paths where they occurred;
• Related Entities — tag buttons for the client, order, transaction, device, zone, or other objects involved. Clicking one opens that entity’s record directly from the modal.

Technical Data Tab

Two JSON blocks:

• Input Parameters — the variables sent with the mutation (contents of the input field);
• Execution Result — either data with the successful result, or errors with the GraphQL error array.

This tab is most useful during incident investigation: you can see the exact values that were submitted and understand precisely what went wrong.

How to Investigate an Incident

A typical scenario: something changed and you need to know who did it and when.

1. Open the Audit Log in organization settings.
2. Set an approximate period using the date filter.
3. In the Operations filter, select the relevant type (e.g. “Update Product”).
4. Review the results — the table shows who performed operations of that type in the selected period.
5. Click the relevant row and open the Technical Data tab — it contains the exact values that were passed at the time of the operation.

If the operation ended with an error (red indicator), the Overview tab immediately shows the error text — explaining what prevented the operation from completing.

Access Permissions

The Audit Log section is visible only to users with the AUDIT_LOG_READ permission at the organization level. This permission is set in roles and access settings and can be granted to owners or specific admin roles.

Only users with this permission can view log entries — an intentional restriction, since the log contains technical operation details including input parameters.

Related Sections

• Roles and Permissions — configure who can see the log
• Shift Handover — shift open and close operations are also recorded in the log
• Team and Staff — manage team composition and role assignments