# "Version history" of an entity

**URL:** <https://community.fibery.io/t/version-history-of-an-entity/9440>\
**Category:** Ideas & Features\
**Tags:** history\
**Created:** [August 22, 2025, 9:33am UTC](https://community.fibery.io/t/version-history-of-an-entity/9440 "2025-08-22T09:33:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [August 22, 2025, 9:33am UTC](https://community.fibery.io/t/version-history-of-an-entity/9440/1 "2025-08-22T09:33:22Z")

</div>

Version history in rich text is very useful. But in entity activity, it tells us what changed when, but you need to manually imagine these changes moving backwards to understand how that entity looked at that point in time.

Notion has a nice version history for pages. Could by nice for Fibery too. Maybe even merging between rich text’s version history and the entity’s version history. No need to have it in two different spots if you ask me.

Linking to related posts, but those are closed as they were focusing on version control of rich text:

> [@Document Changes History](https://community.fibery.io/t/document-changes-history/1730):
>
> We are going to release Docs/Rich Edit text editing history soon, it will work like this: [2021-06-29 16.16.01] Will you miss anything in this implementation? What are your cases for Docs/Rich Edit text editing history?

> [@Versioning in Rich Text Fields (and entities as a whole, too)](https://community.fibery.io/t/versioning-in-rich-text-fields-and-entities-as-a-whole-too/260):
>
> Hi, I think versioning in general is an important feature and versioning of each entity as a whole is not only useful, it is a requirement in certain compliance context. To begin with, the rich text fields should have versioning (and afterwards diff view between versions, revert back to a specific version, etc. too). In general, using an event-sourced architecture greatly helps with features like versioning, undo-redo, etc. Thanks!