Can staff see the audit history?

No, because the page and the export are for the owner only, and any other role is refused before a single row is read.

How do Eva's actions appear?

Under the person column as «Eva» when she carried out the action in a chat or a call, and as «the system» for automatic actions.

Can a card number or password end up in the file?

It should not. Keys that indicate a secret are hidden whatever their value, text that looks like login tokens or secrets is hidden as well, and valid card numbers and IBANs are cut down to their last four digits. The hiding is pattern-based, not an absolute guarantee.

How many rows does the CSV hold?

The latest 10,000 rows under the current filters at most. To export older ones, set a from date and a to date and export again.

Can I tell who exported the file?

Yes, because the export itself is recorded in the history.

Does the history cover integration settings and the control channel?

Yes, there are filter types for both: «settings and integrations» and «messages and control channel», alongside team and permissions, reservations, and projects and prices.

Last updated 2026-10-04

Audit history with CSV: who did what, and when, in your office

The audit history, called «سجل التغييرات» in the dashboard, is an owner-only page listing the sensitive changes the platform records in your office: who changed a price, a lead's owner, a permission or a setting, and when. It can be filtered and exported to CSV. It is included in Agency and only the owner can see it.

Included

Create your workspace

What is it?

The platform records sensitive changes when they happen, and the page shows them newest first in the owner's language: the time in Riyadh time, who did it (the staff member's name, «Eva» or «the system»), the action in Arabic, the record it touched, and before-and-after details. Values that known patterns identify as a password, key or card number are hidden before they reach the screen or the file.

Who is it for?

An owner who wants to know who changed a unit's price or moved a lead from one agent to another.
An office that has added staff and permissions and needs a clear trail of who changed what.
A manager reviewing a reservation, deposit or setting against what really happened.
An office asked for an internal review or statement that wants a CSV it can open in Excel.

What problem does it solve?

Prices or lead ownership change and nobody remembers who did it.
A dispute between staff over a lead or commission needs evidence, not memory.
A raw log is full of technical codes the owner cannot read.
An outside export can leak a secret or card number by accident.

How it works, step by step

Open «سجل التغييرات» from the sidebar. The page is for the owner only, and any other role is sent back to the dashboard before a single row is read.
Read the list: newest first, 50 rows per page, moving with «Newest» and «Older».
Filter by type: leads and assignment, projects and prices, reservations and deposits, buyer portal, broker portal, viewing appointments, launch day, team and permissions, settings and integrations, messages and control channel, property care.
Filter by person: any member of the office, «Eva» or «the system», and by «from date» and «to date» on the Riyadh calendar.
Open a row's details: what changed reads as «from X to Y». Anything resembling a password or token shows as «hidden», and IBANs and card numbers show only their last four digits.
Click «Export CSV» to download a file with Arabic headers and the current filters, which opens in Excel.
The file holds the latest 10,000 rows for the current filters. To export older ones, narrow the date range.
The export is itself recorded in the history, so the owner can see when the file was pulled.

What is included

A newest-first view in Riyadh time, 50 rows per page.
An Arabic label for every action the system writes, with unknown actions shown under their raw name.
Filters for type (11 types), person and date.
«From … to …» details for edits, with anything resembling secrets or card numbers hidden.
A CSV with Arabic headers for the latest 10,000 rows under the current filters.
The export itself is logged.

Limits and fair use

The page and the export are for the owner only. Team leaders and agents do not see them.
The history shows the events the platform writes. Anything the platform does not record does not appear.
The history is read-and-export only. You cannot delete or edit rows from the page.
The export covers at most the latest 10,000 rows under the current filters, and for older ones you narrow the date range.
Some older or new actions may appear under their raw name if they have no Arabic label yet.
The history describes what happened and decides nothing for you. Review and accountability stay with your management.

Price and what others bill you

Item	Price	Billed by
Audit history with CSV	Included	EvaCore

Frequently asked questions

Can staff see the audit history?: No, because the page and the export are for the owner only, and any other role is refused before a single row is read.
How do Eva's actions appear?: Under the person column as «Eva» when she carried out the action in a chat or a call, and as «the system» for automatic actions.
Can a card number or password end up in the file?: It should not. Keys that indicate a secret are hidden whatever their value, text that looks like login tokens or secrets is hidden as well, and valid card numbers and IBANs are cut down to their last four digits. The hiding is pattern-based, not an absolute guarantee.
How many rows does the CSV hold?: The latest 10,000 rows under the current filters at most. To export older ones, set a from date and a to date and export again.
Can I tell who exported the file?: Yes, because the export itself is recorded in the history.
Does the history cover integration settings and the control channel?: Yes, there are filter types for both: «settings and integrations» and «messages and control channel», alongside team and permissions, reservations, and projects and prices.

Related products

Roles and permissionsEach employee sees only what is theirs.Teams, regions and team analyticsOrganise the office into teams and regions and track each team.Outgoing webhooksSend your office's events to your other systems.Lead distribution (auto-assign)Every new lead reaches the right agent by your rules.Analytics and performanceResponse time, conversion and lead sources.