System · Activity & audit
Who changed what.
With the value before and after
For owners, admins and accountants who need to know what happened in the system. Every edit is recorded with the old and the new value, so you no longer guess who overwrote a price or a due date.
- A before/after diff for every edit
- Members, customers, system, cron jobs and API keys as authors
- Records cannot be rewritten or deleted
No credit card. Up and running in 5 minutes.
- 14:32Petra Malá edited invoice FV-2026-0381Payment term: 14 days → 30 days
- 13:05API key “E-shop” created order 2026-04123 items · CZK 24,990
- 11:47Jan Novák assigned the Accountant roleMember: Lucie Dvořáková
- 06:00Scheduled job matched 12 paymentsFio bank statement
- Before and afterEdits show the exact field, the old value and the new one.
- Five actor typesMember, external contact, system, scheduled job and API key.
- ImmutableThe audit record stays even if you delete the entity later.
- Error codesSystem logs carry a code with causes and resolution steps.
Why an audit trail
When something changes, you want to know who and why
A shared system has several people, a connected e-shop and automated jobs working in it. Without an audit trail you investigate from memory and old e-mails.
Today
- Someone changed an invoice price and nobody remembers who
- The record says “edited”, not what changed or from which value
- You learn about a broken integration from a customer
- The error message is a code only a developer understands
With BizKitHub
- Every edit has an author, a timestamp and a value diff
- API and scheduled-job writes are as visible as human ones
- Critical errors arrive by e-mail at once, the rest in a daily digest
- Every error code has causes, a fix and an “Explain with AI” button
Changes with a diff
Not “invoice edited”, but exactly what
The activity detail shows the changed fields with values before and after. It adds request details too: location, network provider, browser and a correlation ID for tracing it in the logs.
- Filter by author, actor type, event type and date
- Minimum severity: info, notice, warning
- When an admin acts as a colleague, both the target and the real author are logged
- An activity timeline on every team member’s profile
| Field | Before | After |
|---|---|---|
| Payment term | 14 days | 30 days |
| Due date | 22 Nov 2026 | 8 Dec 2026 |
| Note | — | Agreed with the director |
System logs
Errors grouped, counted and explained
Identical errors collapse into one row with an occurrence count and a 30-day chart. Each entry carries a code from a catalogue that describes the impact, likely causes and how to fix it.
- Severity from info to critical
- First and last seen, plus related errors in the same component
- Documentation for the code in one click
- “Explain with AI” describes the error in plain language
- PAY_CG_PUSHPayment gateway notification arrived late3×Warning
- EML_QUEUE_FAILE-mail could not be sent from the queue1×Error
- CNT_REG_FAILContact registration failed2×Error
- SEC_ROOT_GRANTEDA member was granted Root permission1×Notice
Alerts
Hear about a problem before your customer does
Critical errors are e-mailed straight away. Once a day the organisation’s admin gets an operations digest: errors, orders, failed payments, e-mail deliverability, firewall rejections and tickets.
- Detects an unusual spike in errors within an hour
- The daily digest can be turned off, critical errors always arrive
- The digest goes to one root member, not a shared mailbox
- Repeated errors are merged so your inbox stays usable
What it does
An audit trail you never have to switch on
Before and after
Changed fields with the old and new value for every edit.
Every author
Member, customer, system, scheduled job or API key.
Identity switching
When an admin acts as a colleague, both people are recorded.
Request details
Location, provider, browser and correlation ID on the record.
Member activity
A timeline of every action on each team member’s profile.
Grouped logs
Identical errors in one row with an occurrence count and chart.
Code catalogue
Impact, causes, fix and documentation for every code.
AI explanations
A plain-language description of an error in one click.
E-mail alerts
Critical errors at once, everything else in a daily digest.
Getting started
Auditing runs from the first minute
- 01
Create an account
Sign-up is free and needs no credit card.
- 02
Work as usual
Every change is recorded automatically, with nothing to configure.
- 03
Find what you need
Filter by person, event or date and get the answer in seconds.
Who it is for
When an audit trail pays off
Owners and management
Check who changed prices, discounts, permissions or payment details.
Accountants
Trace a change on an invoice or order, including the original value.
Integration developers
See exactly what an API key did and where an integration failed.
System admins
Errors, their frequency and how to fix them, in one place.
Connected modules
Runs on the same data as the rest of your company
Team & permissions
Roles, per-module permissions and team invites.
Firewall
Block suspicious IPs and stop abuse.
Security
EU hosting, permissions, audit and firewall.
AI assistant
AI that knows your data and can act on it.
Scheduler
Monitoring for your cron jobs over the API.
API keys
Scoped keys with usage visibility.
Frequently asked questions
Common questions about activity and logs
Do I have to enable auditing?
No. Changes are recorded automatically in every module from the moment the organisation is created.
Can an audit record be edited or deleted?
No. The record is immutable and stays even if you later delete the entity it refers to.
What is the difference between activity and system logs?
Activity records what someone did in the system. System logs capture technical events and errors, such as an undelivered e-mail or a payment gateway outage.
Who receives error alerts?
The daily operations digest goes to one root member of the organisation. You set the addresses for critical error alerts in the organisation settings.
Can I see actions made through the API?
Yes. An API key is its own actor type in the activity log, so changes from your e-shop or another integration are easy to tell apart from your team’s work.
Stop guessing who changed what
Create a free account. The audit trail starts with your first change.