Home/Features/Audit log
Features · Audit log

Who changed it. When. From where. Every action recorded.

The system logs every change automatically — who issued a quote, who edited a contract, who deleted a customer, who changed a password. With the author, date, IP address, city and country (from geolocation). 7 categories, filters, search — GDPR-ready.

Categories
7
Fields per entry
6
Retention
∞
  • Automatic logging
  • IP geolocation
  • Filters + search
  • GDPR-ready

7 event categories, each with its own colour

The system recognises automatically what a change was about. You scan faster and find what you need sooner.

User

Logins, role changes, password changes, adding or removing team accounts.

Company

Edits to company details, logo, tax number, VAT rates and global profile settings.

Branch

Adding a showroom, changing its address, manager or numbering prefixes.

Email

SMTP configuration, adding or removing a sending domain, signature changes.

Template

Changes to measurement, quote and contract templates. Cloning, deleting, edits to blocks.

Merge

Merging duplicate customers and splitting incorrect merges (unmerge).

System

Administrative and automated actions — backups, data imports, archiving.

What the system records in every entry

Six fields that together give the full context: who, what, when, from where. All recorded automatically the moment the action happens.

Author
Full name + email
Action
Full description of the change
When
Date + 'X minutes ago'
IP
Address from HTTP headers
City
Detected from the IP
Country
Full name + flag
Every click leaves a trace

One click in the panel.
Five things in the database.

The system records the action the moment it happens — in a separate `log` table, independent of the main data. It also looks up the city and country from the IP. No input needed from the user.

User action→ Audit log entry
Who
user_id + email
What
action description
When
timestamp
IP
x-forwarded-for
City + country
Looked up from the IP

Everything goes to a separate table, independent of the main data — it doesn't slow down business queries.

Why it matters

Three years later, a data protection inspector turns up.
The question: who had access to a customer's data back in 2023?

Without an audit log you don't know, you can't prove it, and you get fined. With an audit log you search by customer, filter by person and date, and have it in black and white: who, and when. The same goes for employee disputes, customer complaints and internal reviews — every action has an author, a date and an IP address.

Every audit log feature

Logs every change automatically

The backend records an action on every API call that modifies data (POST, PATCH, DELETE). Nothing to switch on — it works from the first login.

IP detection behind a CDN

Reads the x-forwarded-for and x-real-ip headers — works behind nginx, Vercel and Cloudflare. Skips local IPs (192.168.*, 10.*, 127.0.0.1).

IP geolocation

For every IP the system looks up the city and country. No configuration, no API key, free tier of 45 requests per minute.

7 event categories

User, Company, Branch, Email, Template, Merge, System — each with its own colour, badge and description. Easy to scan when reviewing.

Grouped by day

The feed shows entries in groups: “Today”, “Yesterday”, “2 days ago”, “Wednesday 14 May”. A long history is easier to scan.

Search by action

Type “domain” to see every change to the sending domain. Type “carter” to see every change related to the customer Carter.

Filter by user

Pick a person from the “All users” dropdown → you see only their actions. Ideal for reviewing work or during an audit.

Date range

From–to with a calendar. Defaults to the last 30 days; you can go back to any point in the account's history.

Relative time

Instead of “2026-05-30 14:32:17” you see “3 hrs ago”, “yesterday at 14:32”, “2 days ago”. The context is easier to grasp.

Pagination

50 entries per page, page navigation, total event count. Entries never disappear — the full history from the day the account was created.

GDPR

GDPR-ready

Data protection laws such as the GDPR (Art. 32) expect you to show who had access to personal data and when. When a supervisory authority or a customer asks, you filter entries by person and date range.

Branch on every entry

Each entry shows the branch where the change happened. In a network of several showrooms you see straight away where something took place.

Get started

An audit log from day one.

No configuration, no technical knowledge. You log in and work — the system records it. The full history is always available in settings.

Create an account
GDPR + security

Check whether our audit log meets your requirements.

How we process data, who has access to it and what rights the people it concerns have — described in one place.

Security and GDPR