# Whiteboard as context (= information) – how to use this 'insight' in Fibery? **URL:** \ **Category:** Get Help\ **Created:** [August 22, 2024, 9:14pm UTC](https://community.fibery.io/t/whiteboard-as-context-information-how-to-use-this-insight-in-fibery/6536 "2024-08-22T21:14:19Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\ **Post date:** [August 27, 2024, 10:15am UTC](https://community.fibery.io/t/whiteboard-as-context-information-how-to-use-this-insight-in-fibery/6536/12 "2024-08-27T10:15:00Z")
Hi @lerone and welcome to the Fibery forum and right away with such an interesting discussion! 🙂 I have a simple mind, and so I definitely am not sure that I understood everything you are describing, but one thing I think I understood is: **You want to see which Whiteboards an Entity is embedded on.** Is that correct? Entities do have a field that shows `Referenced x times`, which shows the Entities, where a link has been placed. If I gather correctly, you would like to also see the Whiteboards listed there. Would that solve one of your challenges? ## Warning: Potential Thread Hijack 🙊 (Happy to move this into a different thread) The other interesting idea that your discussion triggered for me (alongside with [this one on Whiteboards](https://community.fibery.io/t/entities-relations-to-whiteboards/6507)): Certain aspects of specifications have rather structured data, I usually handle this through [text tables](https://community.fibery.io/t/weve-improved-docs-greatly-this-year-do-you-still-really-miss-something/4972/31). So if we take for example specs for: - Data Objects - UI Screens - API Calls - Reports All these make a nice table with rich text and Entity references. One could argue that this could be a Table View, but that will be too limiting. **Instead, what I would LOVE to be able to do is to add a Rich Text Field with a Schema Table.** This could be a different type, or an extension of the existing table. The gist would be that I can define a column (or row) to be schematised in the sense that any mentioned Entity of a given Type automatically gets connected through a ordinal relationship. So the schema of the column (or row) specifies how the mention gets connected. Maybe an example helps, looking at a UI screen spec - A Screen has multiple Components - Each Component will display one type of Data Objects (one or more) - Each Component will also have Actions, UI Strings, etc. As such, a Screen Entity could have a table (e.g. User Profile): | Component | Data Object | Description | Actions | | --- | --- | --- | --- | | #Nav Header | - | Standard navigation header | _See Component_ | | #Breadcrumbs | - | Standard breadcrumbs bar | _See Component_ | | #User Profile Card | #User | Displays the key user details: Pics, name, email | Click `Edit` → #Edit Profile Screen | | #Action Bar | - | Other actions that can be taken on the page | Click `Change Email` → #Change Email Screen, `#Delete Account` → #Delete Account Screen | In the above table I used `#` to indicate all Entity Mentions. Each of the columns would be configured as follows: - `Component`: Any mention links this Screen Entity to a Component Entity (n-n) - `Data Object`: Any mention links this Screen Entity to a Data Object Entity (n-n) - `Actions`: Any mention links this Screen Entity to a Screen Entity (n-n) Of course, all these Relationships would have to first be configured on the Entity level. Overall, this would allow for a more rich text and a more dynamic blend between structured and unstructured data. It would also allow me to hide a way a number of Views, as I now can dynamically generate some of these tables. Again, sorry if this message side-tracks the thread. 🙊 --- _[View the full topic](https://community.fibery.io/t/whiteboard-as-context-information-how-to-use-this-insight-in-fibery/6536)._