> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Show Record Change History as a Chat
- URL: https://blog.jestor.com/record-change-history-as-chat/
- Published: 2026-09-17T22:29:43.000Z
- Updated: 2026-09-17T22:29:43.000Z
- Author: Bruno Bannach

Displaying **record change history as a chat** puts every modification to a record in a readable timeline, inside the card, rather than in a separate log nobody opens.

## Why change history goes unread

History exists in most systems. What it usually lacks is a format anyone wants to look at.

- Logs formatted for machines rather than people
- No sense of sequence when reviewing changes
- History reachable only through a separate area
- Information exposed to people who should not see it

## What you control on the updates tab

- **Whether it appears at all** — it is disabled by default
- **Whether updates also post to the chat**, as they did previously
- **Whether only builders can see it**, restricting sensitive information
- **Where it lives** — a dedicated tab rather than a toggle inside history

## How to configure it in Jestor

1. Open the form editor in **Jestor** for the card in question.
2. Find the updates option among the card tools.
3. Enable it — it is off by default, because it exposes information you may not want everyone to see.
4. Choose whether updates should also be sent to the record's chat.
5. Restrict visibility to builders where the information is sensitive.

## Why choose Jestor for transparent records?

**Jestor** made the default deliberately conservative: change history is off until someone decides it should be visible, because a record's modification log can reveal more than a process intends.

Alongside the per-table history view and its export, this gives three levels — visible in the card, searchable per table, and exportable for audit.

## Frequently Asked Questions

### Why is the updates tab off by default?

Because it can expose information not everyone should see.

### Can updates still go to the chat?

Yes, the previous behaviour remains available. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can I limit it to builders?

Yes, visibility can be restricted.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

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](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.