How to audit changes to your data
To audit changes to your data, you need more than a list of edits. You need to know what changed, when, and whether it came from a person, an automation or the API. In Jestor, a history view sits inside the table itself, filtered to that table's records.
Why a global log is hard to use
An account wide history contains everything, which makes it technically complete and practically unusable. Finding what happened to one table means scrolling past everything that happened everywhere else.
Filtering the log to the table you are looking at changes it from an archive into a tool.
Questions an audit view answers:
- What changed in this table recently
- Who made a specific change
- Whether a deletion was intentional
- Whether a value was set by a person or an automation
- What happened on a particular day
What you can filter by
| Filter | What it isolates | Typical question |
|---|---|---|
| Action type | Update, deletion and others | Did someone delete records? |
| Source | User, automation or API | Was this a person or a rule? |
| Date | Today, yesterday, earlier | What happened before the error? |
| Advanced filters | Narrower combinations | A specific investigation |
Step by step to investigate a change
- Open the table where the data lives.
- Go to the views area and select history.
- Filter by date to narrow to the period in question.
- Filter by action type, separating updates from deletions.
- Filter by source to determine whether a person, automation or API made the change.
- Export the log when the investigation needs to be shared or kept.
Why knowing the source matters most
The single most useful filter is the one that separates a person from an automation. If an automation is setting a value incorrectly, the fix is in the rule. If a person is, the fix is in training or permissions. Those are entirely different responses, and the log is what tells you which one applies.
- Scoped to the table: only the records you are investigating
- Source identified: user, automation or API
- Deletions visible: not just updates
- Exportable: the log can leave the platform when needed
Frequently Asked Questions
Can I see the history for just one table?
Yes. The history view inside the table is filtered to its records. See jestor.com.
Can I tell whether an automation made a change?
Yes. The log identifies whether the source was a user, an automation or the API.
Can I export the log?
Yes. The filtered history can be exported.
Video Tutorial: Step by Step
With Jestor, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.