# Allow highlights to be created in ANY rich text field, not requiring entity to be of Source database

**URL:** <https://community.fibery.io/t/allow-highlights-to-be-created-in-any-rich-text-field-not-requiring-entity-to-be-of-source-database/6362>\
**Category:** Get Help\
**Created:** [July 6, 2024, 6:29pm UTC](https://community.fibery.io/t/allow-highlights-to-be-created-in-any-rich-text-field-not-requiring-entity-to-be-of-source-database/6362 "2024-07-06T18:29:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [July 6, 2024, 6:29pm UTC](https://community.fibery.io/t/allow-highlights-to-be-created-in-any-rich-text-field-not-requiring-entity-to-be-of-source-database/6362/1 "2024-07-06T18:29:11Z")

</div>

Currently, the Highlight feature mandates that the entity containing the rich text field is part of a Source database. This setup restricts the flexibility of where highlights can be applied. The Highlight configuration has a limit of source databases.

Would it be possible to allow highlights to have either have a ‘default’ source database, not just the one inherently associated with the current entity? Or, that the source database is not present at all?

Could this be achieved by adding explicit `sourceTypeId` and/or `targetTypeId` attributes in the Highlight configuration within the JSON structure?

The idea is that the Highlights feature could be more universally used in rich text fields.