Audit Log
Summary
Path: "Settings" -> "Change Log". The change log shows an audit of the activities in the project.
What is recorded
- project;
- agent;
- channel;
- participant;
- MCP server;
- list of servers;
- data source;
- documentation;
- knowledge base;
- project variable;
- definition of the lead variable;
- segment;
- segment consent document;
- landing;
- trigger;
- delivery;
- tariff;
- invitation.
Types of Actors
- user;
- administrator;
- system;
- API key;
- application;
- agent.
Types of actions
- created;
- updated;
- deleted;
- transferred.
On the card you can see
- who made the change;
- When;
- what entity was changed;
- which fields have changed;
- value before and after;
- the full value in a separate dialog, when available.
What is hidden or grouped
The log hides service fields that do not help explain a user action.
Secrets and very large values are also hidden. Tokens, connection keys, large draft content, attachments, and other sensitive data cannot be viewed through the log.
For segments, the log separately shows changes to the public identifier and consent documents. For landings, it shows list visibility and Telegram menu button settings.
For deliveries, the log records the name, status, message text, and scheduled start time. Audience filters and attachments may be hidden because of their size.
For a project member, changing the role groups the related permissions. The log may therefore show one role change instead of every permission separately.
For the question "who changed the settings"
- open “Settings” -> “Change Log”;
- use an entity type filter if you know what changed;
- if the period is known, limit the search by time.
Where this is in the interface
Main elements in this section:
- project settings page
- change log page
- change log filters
- Settings item in the side menu