← Back to the blog

Why editing data directly in a database should leave an audit trail

However well a system is designed, there are days when data must be fixed by hand: a mistyped address, or an order status to roll back. The trouble starts when nobody knows who changed what, and when.

What to record

  • Who made the change and when
  • The table and rows changed
  • The values before and after
  • The request behind it, so edits to many rows at once can be seen together

The record must not be editable

An audit log that users can edit or delete is worthless for review. It should be written only from the server side and read by people with the right to see it.

In Ruamhub

Edits to data, table structure, pipelines and member roles are recorded automatically. You can filter by category and period and export to CSV. Retention depends on the plan.

Bring all your databases into one place

Start free, or book a demo and we will walk through it with your own team’s data.