تخطَّ إلى المحتوى

Audit Log — Staff Action History in IZI

Опубликовано: · Обновлено: (6 дней назад)· IZI Team

هذا المحتوى غير متوفر بلغتك بعد.

IZI writes every data change an employee makes through CRM to the audit log: who, when, which operation, in which club and how it ended. The log is there for incident investigation — for example, when a product disappears from the catalog or someone changes a tariff price. CRM has no separate log screen: entries are requested from IZI support, while the owner sees operations with client money directly in club analytics.

An operation is recorded when three conditions are met:

  • it was performed by an employee signed in to CRM;
  • it changes data — creating, editing, deleting, taking a payment. Viewing pages and reports is not logged;
  • the operation is on the logged list — built automatically from the IZI schema and extended with new features.

Each entry keeps:

WhatExample
TimeWhen the operation was performed
EmployeeWho performed it
OperationFor example, editing a product, cancelling a purchase, crediting bonuses
ClubThe club where it happened, or the whole organization
ResultSuccess or error
ParametersThe values the operation was called with

The entry is written at the moment of the operation and does not depend on the log storage being available: if the storage is temporarily down, entries queue up and are moved later, nothing is lost.

Entries are kept for up to 180 days. If an incident needs investigating, ask right away — an entry older than six months cannot be recovered.

  1. Note what changed, in which club and roughly when: the date and time window.
  2. Contact IZI support from the club chat or via Support in the CRM user menu — it opens the support bot — and pass on these details.
  3. Support finds in the log who performed the operation, when, and with which values.

The operations that raise questions most often — manual credits, debits and compensations — the owner sees in CRM directly: club Analytics → Control.

ReportWhat it shows
Manual operationsManual credits and debits of gaming and bonus balance by employee
CompensationsPlaytime compensations with the granting employee’s name, the client’s phone and the comment

The same section has device analysis and the tech mode log. Access to Control requires the Suspicious Activity Report permission. See Access permissions.

In the role editor, in the organization General settings group, there is an Audit Log checkbox — the right to read the organization’s log. CRM currently has no log screen, so this permission does not open any new sections.

الأسئلة الشائعة

What does the IZI audit log record?

Every data change an employee made through CRM: who, when, which operation, in which club and with what result. Reading data is not logged.

Where in CRM do I open the audit log?

CRM has no separate audit log screen. The log is kept for incident investigation: if you need to find out who changed data and when, contact IZI support. Operations with client money are visible in CRM in the Control analytics section.

How long are log entries kept?

Up to 180 days. Older entries are removed from the log storage.

What does the Audit Log permission in the role editor do?

It is the right to read the organization's log. CRM currently has no screen for viewing the log, so it does not change what the employee can do in CRM.

How do I find out which admin credited money or bonuses to a client?

Open club Analytics → Control → Manual operations: manual credits and debits are listed by employee. Playtime compensations are in the Compensations report with the granting employee's name.

About IZI