# Named Versions in Docs and Rich-Text Field History

**URL:** <https://community.fibery.io/t/named-versions-in-docs-and-rich-text-field-history/1856>\
**Category:** Ideas & Features\
**Tags:** history\
**Created:** [July 30, 2021, 2:55pm UTC](https://community.fibery.io/t/named-versions-in-docs-and-rich-text-field-history/1856 "2021-07-30T14:55:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [July 30, 2021, 2:55pm UTC](https://community.fibery.io/t/named-versions-in-docs-and-rich-text-field-history/1856/1 "2021-07-30T14:55:51Z")

</div>

Sometimes it is useful to add Named Versions to quickly find them later and see the changes.

> [@Document Changes History](https://community.fibery.io/t/document-changes-history/1730/6):
>
> 100% agree with @Simon_JB and @Matt_Blais that a “highlight changes” will be important for this feature, at least long-term. Initial release can be without that, but to really be a good implementation it should have version differencing, ideally between arbitrary versions, but at least between immediately successive ones. Once again I’d point to Discourse as a pretty good implementation. wink Although I don’t think it does arbitrary version comparison (that one’s not a must though, as I say). …

> [@Document Changes History](https://community.fibery.io/t/document-changes-history/1730/8):
>
> DEFINITELY THIS sparkling_heart I find named versions indispensable in Google Docs. We use Google Docs to author web page content, and I make a version name for a doc whenever I upload its contents to the web page (“Uploaded to website [date] - Matt”). That way I can quickly check the doc’s version history to see if it has been modified since I uploaded it to the web page. Super useful!