# Entity view in a document

**URL:** <https://community.fibery.io/t/entity-view-in-a-document/3548>\
**Category:** Ideas & Features\
**Tags:** blocks, rich-text\
**Created:** [November 17, 2022, 10:13pm UTC](https://community.fibery.io/t/entity-view-in-a-document/3548 "2022-11-17T22:13:27Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [November 20, 2022, 8:57am UTC](https://community.fibery.io/t/entity-view-in-a-document/3548/10 "2022-11-20T08:57:36Z")

</div>

tldr: embedding ≠ integrating

I wasn’t trying to suggest that Fibery can do everything that a spreadsheet can do, not even close. But when we talk to users about what they use Google sheets for (in a work management context) it is often something that can already be done in Fibery. Hence…

> [@Chr1sG](#):
>
> good enough substitute for most use cases

However, for the cases where a spreadsheet is the right tool for the job, embedding a view of a Google sheet is totally different to integrating/syncing with it.

What is gained by implementation of the former? Yes, it probably means that a user can work on a sheet from within a Fibery document (compared with switching browser windows) but it provides no real ‘connectivity’ between the two data silos.

On the other hand, I can see much more value if Fibery were capable of syncing data from Google sheets (like it can with Airtable).  
Then a user can user can utilise the spreadsheet format when appropriate, and leverage the results from within Fibery (presented if necessary in a Fibery document using embedded table view or report view).

---

_[View the full topic](https://community.fibery.io/t/entity-view-in-a-document/3548)._