# Audit log in a CRM: how to see who changed what and when

https://krokul.com/en/blog/crm-audit-log/ · Krokul Team · Updated 2026-11-19

Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. Its Audit screen answers who changed an amount, moved a deal or edited a setting, with the time and the value before and after.

**Short answer.** A CRM audit log is a list of changes with their author and time, and with the value before and after for fields and stages. To find who changed a deal amount, filter the log by entity, type of change and period, expand the event, read the old and new value and open the record. Review it monthly.

## When you need a CRM audit log

An audit log pays for itself the first time a number changes and nobody remembers why. The guide on [connecting AI agents and other tools to a CRM safely](https://krokul.com/en/blog/topics/crm-ai-agents-integrations/) explains why every channel that writes to the CRM must leave a trace, and the log is where those traces are read.

- A deal amount dropped the day before signing and the sales manager says it was not them.
- A stage moved forward and a quote went out before the required fields were filled.
- A price list or a pipeline setting changed and the numbers in the reports shifted.
- A colleague exported all clients and you need to know when and how many rows.
- An automation or an integration created records and you need to tell it from a person.

- **Audit log** — An audit log is a list of events in the CRM in which each entry says who did what, when, and to which record.
- **Before and after** — Before and after is the pair of values of a field, such as an amount from 300 to 400, that the log keeps for each change.
- **System actor** — A system actor is an automation, an integration or a background process that acts in the CRM without a person.

## How to find who changed what in six steps

Finding who changed what takes six steps: write the question down, narrow the log to one entity and period, find the event, read before and after, tell people from systems and open the record. Narrowing first matters, because a company log holds thousands of entries.

### 1. Write the question as one sentence

State the record, the field and the rough time, for example the amount of one deal in the last week. A precise question tells you which filter to start with.

If you only know the symptom, such as a changed report number, start from the type of change and work backwards.

### 2. Open the log and narrow it by entity and period

Choose deals, contacts or clients as the entity and set the period. Day boundaries follow the time zone of the company, so one day from start to end covers that calendar day for your team.

For one person’s work, filter by author instead.

### 3. Filter by the type of change

Pick the type that matches the question: a changed field, a stage change, a deletion, a changed dictionary or a document status. A narrow type removes the comments, calls and emails that fill the rest of the feed.

Use the search box for a name or a word once the list is short.

### 4. Expand the event and read before and after

A field change reads as the field name, the old value and the new value, and a stage change as the old stage and the new one. Compare the time with what you remember, because a change made minutes before a document went out tells a different story from one made a month earlier.

Load older events when the entry you need is not in the first page.

### 5. Tell a person from a system

Entries made by people carry the name of the author, and entries made by automations, integrations and background processes carry a robot mark. A change by a robot points you to a rule or an integration.

Settle the rule first, then talk to the person who owns it.

### 6. Open the record and decide what to fix

Follow the link from the event to the deal, contact or client and look at the record as it stands now. Restore the value by hand if it is wrong, and write a note in the record so the next reader knows.

Then fix the cause: a role that was too wide, a rule that wrote the field or a process nobody owned.

![Version list of an integration rule with the author and time of each version](https://krokul.com/img/en/blog/crm-audit-log-rule-versions.webp)

## Which filter answers which question

Most questions about changes fit one of a few filter combinations. The rows below are an example for an integrator that runs deals, projects and invoices in one system, so replace the questions with your own.

Example: audit questions, the filters to start with and what to read:

| Question | Filters to start with | What to read |
|---|---|---|
| Who changed the amount of a deal? | Entity: deals, type: changed field | The amount line with old and new value |
| Who moved a deal to the quote stage? | Entity: deals, type: stage change | The stage line and the time |
| What did one colleague do last week? | Author and period | Every entry of that person |
| Who changed a dictionary or a setting? | Type: changed dictionary | The expanded event |
| Who exported clients and when? | Type: export | The object, the format and the number of rows |

## Which audit mistakes to avoid

- Reading the log only after an incident means nobody knows the normal picture, so scan it once a month.
- Starting without a filter buries the answer, so choose the entity and the type first.
- Sharing one login between colleagues gives entries without a real author, so give each person a seat.
- Blaming the last person who touched a record misses automations, so check the robot mark before you ask a colleague.
- Searching the whole history with the search box misses older events, so load older entries or narrow the period.

## A monthly audit checklist

- Changes of fields and stages in your key deals each have an author you recognise.
- Dictionary and setting changes match what the team agreed.
- Exports have a named author and a reason.
- Deleted deals and contacts are known to the person who owns them.
- Entries marked as made by a system belong to rules you can name.

## How the Audit screen works in Krokul

The Audit screen shows the events of the whole company, newest first, 50 at a time, with a Show older button. Filters cover the period, the author, the type of event, the entity and a search box. Within the type filter there are 31 types, from creating, changing, deleting and merging a record to a changed field, a stage change, a payment, a printed document, a new document version, a renewed subscription, a changed dictionary and an export.

Expanding an event shows lines such as the field, the old value and the new value, and a stage change reads as the old stage and the new one. Open takes you to the deal, contact or client when the event belongs to one. Changes of dictionaries and settings belong to no record. Entries from automations, integrations and background processes carry a robot mark instead of an avatar. The search box and the entity filter narrow only the events that are already loaded, so press Show older when the entry is not there.

Exports are logged with the object, the format and the number of rows, and a deleted deal or contact leaves a line with its name, which is the only trace in the log of a record that is gone. Within the retention period the record itself can return, as described in the guide to restoring deleted CRM records. The Audit screen has no way to edit or delete an entry, and records of changed fields, stage changes, changed dictionaries, deletions and exports cannot be edited at all. Administrators and managers read the log. Agents and read-only users do not see the item, and a direct link tells them that the log is read by administrators and managers. An agent still sees the history of their own records in the activity feed of each card, and the roles that keep cost and margin private follow the same split.

A part of the same log is available through the API route report/api-audit for administrators and managers. By default it returns changed fields, stage changes and deletions, and on request changed dictionaries and exports, up to 200 entries a page with a cursor to the next one. The Krokul page on [roles, audit log and change history](https://krokul.com/en/solutions/security/) describes the rest of the security model. The guide on [safe AI access to CRM data](https://krokul.com/en/blog/ai-assistant-safe-crm-access/) covers scopes, roles and the log for automated access.

## Frequently asked questions

### What is the difference between an audit log and a record history?

A record history shows what happened to one deal, contact or client, and an audit log lists events across the whole company with filters. Krokul has both, and the Audit screen is the company-wide one.

### Can I see who changed the amount of a deal in Krokul?

Yes. Filter the Audit screen by deals and by the type changed field, expand the event and read the line with the old and the new amount, the author and the time.

### Can someone remove a change from the audit log?

Not from the Audit screen, which offers no way to edit or delete. Records of changed fields, stage changes, changed dictionaries, deletions and exports cannot be edited in Krokul.

### Does the log show what automations and integrations did?

Yes. Their entries carry a robot mark instead of the avatar of a person, so you can tell a rule from a colleague.

### Who can open the audit log?

Administrators and managers. Agents and read-only users do not see the Audit item.

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs
