# Entity-based versus native for Docs, Comments & References

**URL:** https://community.fibery.io/t/entity-based-versus-native-for-docs-comments-references/7932
**Category:** Get Help
**Created:** [December 10, 2024, 9:03pm UTC](https://community.fibery.io/t/entity-based-versus-native-for-docs-comments-references/7932 "2024-12-10T21:03:47Z")
**Posts on this page:** 1
**Showing post:** 4

<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: [February 19, 2025, 10:54pm UTC](https://community.fibery.io/t/entity-based-versus-native-for-docs-comments-references/7932/4 "2025-02-19T22:54:10Z")

</div>

Agreed and adding +1 about permissioning. Since comments are not exposed as a database, we cant limit who can or can not see the related comments.

“UI will be quite bad, unintuitive, etc. And you will not gain much having comment as a database. BTW, what exactly you need?”

What if you set create a “tread view” which is showing entities but in a thread view like comments, but in reality they are just entities, not comments under the hood?

---

_[View the full topic](https://community.fibery.io/t/entity-based-versus-native-for-docs-comments-references/7932)._