# Versioning in Rich Text Fields (and entities as a whole, too)

**URL:** <https://community.fibery.io/t/versioning-in-rich-text-fields-and-entities-as-a-whole-too/260>\
**Category:** Ideas & Features\
**Tags:** history\
**Created:** [June 13, 2019, 1:33pm UTC](https://community.fibery.io/t/versioning-in-rich-text-fields-and-entities-as-a-whole-too/260 "2019-06-13T13:33:57Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [August 7, 2020, 11:05am UTC](https://community.fibery.io/t/versioning-in-rich-text-fields-and-entities-as-a-whole-too/260/6 "2020-08-07T11:05:16Z")

</div>

As an add-on to this request, when it’s implemented, I’d appreciate the ability to be able to make relationships that are version-specific.  
Ideally, I can choose to create a link that is either:

- to the entity in general, independent of what versions exist
- to a specific version of the entity, including current version (but which may not remain current)  
Hope you understand what I mean.

---

_[View the full topic](https://community.fibery.io/t/versioning-in-rich-text-fields-and-entities-as-a-whole-too/260)._