# July 25, 2024 / Entity access explained, markdown import, hidden Fields section **URL:** \ **Category:** Changelog\ **Created:** [July 25, 2024, 1:11pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434 "2024-07-25T13:11:05Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [July 25, 2024, 1:11pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/1 "2024-07-25T13:11:05Z")
## Understand who has what access to Entity and why ![entity-access-explained](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0a1450f270c93ef09dabf979f108a268a5009da2.gif) There are numerous ways how someone might receive access to a Feature, Task, or Client: - via [Space sharing](https://the.fibery.io/@public/User_Guide/Guide/Share-Space-232); - via direct [Entity sharing](https://the.fibery.io/@public/User_Guide/Guide/Share-Entity-233); - via extended Entity sharing using [custom access templates](https://the.fibery.io/@public/User_Guide/Guide/Custom-Access-Templates-240); - via [automatic sharing to assigned users](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-with-Assignees-327). All of these sources combine and merge, making it hard to tell the final access for a given person. Does everyone who should have access have it? Is there someone who shouldn’t have permissions but does? To make the access audit easier, we’ve introduced a drill-down to individual users and capabilities. Expand a particular user to see where a certain capability has come from. ## Automatically share Entities with those who create them ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/956a8ecc4a9a65d8ca5752e949fc64ec9fa5a1c5.png) Previously, `Created By` has been excluded from the [automatic sharing via user relations](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-with-Assignees-327) — now it joins the party. Author access will become truly useful with the upcoming Database access but there is one use case that already makes sense: enable the automatic access for Entity creators to ensure they won’t lose access to their creations in case their access to the parent Space is downgraded or revoked. Unlike other relations, access via `Created By` doesn’t support custom access templates or extending access. On the bright side, the author access can be revoked per Entity without clearing the Field value. ## Import markdown and plain text files into a database ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f39d6789430e885b27bb268f050f507ea6d526e5.png) You can import a markdown file or a zipped markdown file structure directly into an existing or new Fibery database instead of importing them into a document. Databases over documents have many advantages, so we encourage our users to use this method. ## Paste markdown into Fibery’s editor ![paste-md-into-fibery](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/71f44fc855d34e4504ef82d08b180d6d58a26e31.gif) In addition to a full-scale [import of markdown files](https://the.fibery.io/@public/User_Guide/Guide/Import-from-Markdown-187), we now also support simple copy-paste of markdown from another tool. Paste a markdown doc into Fibery’s editor — and it will automatically be formatted. If you don’t want the automatic formatting, paste using the `Cmd+Shift+V` keyboard shortcut or use the code block. ## Hide empty Fields from Entity View ![hide-when-empty-entity-view](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/54d19b0e1de8a1f977aba2f634ed7624c8e3a4fb.gif) The `Hide when empty` Field setting is now available on the Entity View. Selectively hide Fields in Compact sections when their value is empty to streamline the UI. As usual, this option is available under the `Manage Fields & Layout` menu and works for both 1-column and 2-column layouts. When some Fields are hidden, a collapsible section appears so you can access those Fields. ## 🦋 One-liner improvements - **Automations:** we’ve replaced GPT 3.5 with GPT-4o-mini as the default model. - **Integrations:** when editing integration settings, if you click away from the window, a popup will appear, asking if you want to discard changes or continue editing. This prevents accidental loss of unsaved settings. - **Integrations:** we’ve added `Edit Fields to the Sync` menu item to the DB’s context menu to quickly access the integration Field mapping. With this change, you will save at least four unnecessary clicks. ## 🦐 Fixed Bugs - Whiteboard: child entity doesn’t get linked to the parent if you draw relation line from parent and add child via search - Don’t show `No value` placeholder in edit mode for numbers - Mentions: setup units button is available for users who don’t have permissions to edit it - Self-Relations `Unlink All` doesn’t unlink all and Relations popup doesn’t show every relation ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [July 25, 2024, 1:11pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/2 "2024-07-25T13:11:23Z")
---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [July 25, 2024, 1:57pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/3 "2024-07-25T13:57:43Z")
> [@antoniokov](#): > > ## Hide empty Fields from Entity View Thank you for this. Somewhat related in terms of hiding things to streamline UI - are there plans to allow to hiding of the “No Entity” rows in smart folders that have multiple levels? I really don’t understand why it doesn’t get hidden automatically if there’s no orphan entities found. ![testsite-ca-—-Site-Fibery](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/62ae32255d5e133f22c9be167483959f96c13c52.jpeg) ---
**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:** [July 25, 2024, 4:36pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/4 "2024-07-25T16:36:18Z")
Nice work! Hope that allows me to troubleshoot why entities I created today were not visible to my teammate who was assigned. 🙂 ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [July 25, 2024, 4:39pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/5 "2024-07-25T16:39:05Z")
> [@antoniokov](#): > > Hide empty Fields from Entity View Really like this one! 😍😍 However: I just noticed that for all formulas the setting ‘hide when empty’ has been turned on. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/dde0622f20c6b3005a349df65ec5aac0d31b3736.png) This really ruins our workspace 😅 We have very detailed wikis per entity which explains how fields are working, when to use what etc. We always start with ‘fields on top of the screen’ and explain from top to bottom each field. Currently all formulas are hidden by default, which is very confusing since the screen doesn’t match with the wiki anymore. We already had big problems after the release of ‘total rows’. Since the total rows were turned on for each view although it wasn’t applicable. _(We’ve needed to change/check more than 500 context/relation views and we still find total rows in places (like embedded views) that don’t make any sense. Plus the settings are not part of the template so we need to change it for each client that we onboard (as a partner). Which is not doable and therefor we are postponing to onboard them)._ Please don’t let us need to check all (hundreds) formulas in the workspace to manually undo the ‘hide when empty’ setting 😅 And more overall: please don’t release changes that impact current views/settings/behavior that suddenly changes the whole workspace after a release. That’s the recipe for a panic attack (both for admins as for users) 🙈 ---
**Author:** ![Fabrice\_Tropenat](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/fabrice_tropenat/32/4686_2.png) [@Fabrice\_Tropenat](https://community.fibery.io/u/Fabrice_Tropenat)\ **Post date:** [July 25, 2024, 4:41pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/6 "2024-07-25T16:41:14Z")
Happy to see new Improvements on entity access that can be configured through many ways. However it seems to me we are still missing the obvious « database level » permission feature. When do you expect to implement it ? ---
**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 25, 2024, 6:30pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/7 "2024-07-25T18:30:03Z")
All of the features introduced in this release are pretty powerful, thank you!. They solve a number of my standing issues. 🤗 ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [July 25, 2024, 6:49pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/8 "2024-07-25T18:49:53Z")
Hooray for much better Markdown import/overall support! 🙌 ---
**Author:** ![Minh\_Tri\_Do\_Hang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/minh_tri_do_hang/32/6791_2.png) [@Minh\_Tri\_Do\_Hang](https://community.fibery.io/u/Minh_Tri_Do_Hang)\ **Post date:** [July 26, 2024, 2:52am UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/9 "2024-07-26T02:52:18Z")
> [@antoniokov](#): > > ## Paste markdown into Fibery’s editor > > ![paste-md-into-fibery](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/71f44fc855d34e4504ef82d08b180d6d58a26e31.gif) > > In addition to a full-scale [import of markdown files](https://the.fibery.io/@public/User_Guide/Guide/Import-from-Markdown-187), we now also support simple copy-paste of markdown from another tool. > > Paste a markdown doc into Fibery’s editor — and it will automatically be formatted. If you don’t want the automatic formatting, paste using the `Cmd+Shift+V` keyboard shortcut or use the code block. Finally, thank you for fixing this ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [July 26, 2024, 6:56am UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/10 "2024-07-26T06:56:26Z")
> [@YvetteLans](#): > > I just noticed that for all formulas the setting ‘hide when empty’ has been turned on. Before this update, we _always_ hid read-only Fields with empty values, including formulas, irrespective of your `Show empty values` View setting. Now they are hidden when empty by default but you can change that. So nothing should have changed on your Views with the update. If it has, please ping us via Intercom and let’s troubleshoot. > [@YvetteLans](#): > > please don’t release changes that impact current views/settings/behavior that suddenly changes the whole workspace after a release We understand that every breaking change has its cost and usually we manage to avoid those. Can we guarantee that breaking changes won’t _ever_ happen? Certainly not. Sometimes we believe the majority of users benefit from an update and we roll it out en masse. Sometimes the cost of a seamless migration is so high, that we decide to ignore some edge cases. If we had never released a breaking change, Fibery would have been a much worse product now. ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [July 26, 2024, 6:57am UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/11 "2024-07-26T06:57:44Z")
> [@Fabrice\_Tropenat](#): > > However it seems to me we are still missing the obvious « database level » permission feature. > When do you expect to implement it ? Unless something goes terribly wrong, in the next couple of months. The development has already started. ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [July 26, 2024, 7:37am UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/12 "2024-07-26T07:37:30Z")
> [@antoniokov](#): > > Before this update, we _always_ hid read-only Fields with empty values, including formulas, irrespective of your `Show empty values` View setting. Not for 1 column views. > [@YvetteLans](#): > > please don’t release changes that impact current views/settings/behavior that suddenly changes the whole workspace after a release What I mean is: “When you release settings; don’t just turn things on when that wasn’t the case”. > [@antoniokov](#): > > If we had never released a breaking change, Fibery would have been a much worse product now. That I understand since I have an IT background. So it’s just about the settings ❤ I’ve send you guys a message via Intercom! ---
**Author:** ![Zauri](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/zauri/32/9109_2.png) [@Zauri](https://community.fibery.io/u/Zauri)\ **Post date:** [July 26, 2024, 10:00am UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/13 "2024-07-26T10:00:46Z")
Hey! We will push a hotfix to disable this setting by default (including read-only Fields) for Entity View 🙏 ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [July 26, 2024, 12:24pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/14 "2024-07-26T12:24:43Z")
Awesome, thank you so much! 😍 ---
**Author:** ![mz\_et](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mz_et/32/9561_2.png) [@mz\_et](https://community.fibery.io/u/mz_et)\ **Post date:** [July 31, 2024, 8:26pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/15 "2024-07-31T20:26:22Z")
Re: Sharing… has anyone asked for the ability to share items on a per item basis, but still see underlying data? For example: we would like to share specific roadmaps and views with our leadership. But to do so, they (seem to) have to have access to the underlying data (products, components, features, feedback), meaning that they see more than we’d like to them to. Thanks! ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 1, 2024, 7:05am UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/16 "2024-08-01T07:05:04Z")
Views sharing is one of the last item in our permissions scope. So far it is not possible to do that easily. One workaround is to create a separate entity like Public Feature and copy SOME data from Feature via automation rules. Then you can give access to this Space and Features data will be hidden. ---
**Author:** ![mz\_et](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mz_et/32/9561_2.png) [@mz\_et](https://community.fibery.io/u/mz_et)\ **Post date:** [August 1, 2024, 11:55am UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/17 "2024-08-01T11:55:17Z")
We don’t mind that people would have access to data… it’s other Spaces that we’d like to hide. For example, we want to put these roadmaps and views in a separate Space and only allow leadership to see things in that Space; not the Space where the data actually resides. I’m not sure if this would help you narrow the scope of your permissions update. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 6, 2025, 2:36pm UTC](https://community.fibery.io/t/july-25-2024-entity-access-explained-markdown-import-hidden-fields-section/6434/18 "2025-11-06T14:36:52Z")
> [@interr0bangr](#): > > Somewhat related in terms of hiding things to streamline UI - are there plans to allow to hiding of the “No Entity” rows in smart folders that have multiple levels? Now you can hide it > [@November 6, 2025 / Contributor Space access is being deprecated, Edit entities you create, Hide empty "No parent" groups](https://community.fibery.io/t/november-6-2025-contributor-space-access-is-being-deprecated-edit-entities-you-create-hide-empty-no-parent-groups/9967): > > Contributor Space access is being deprecated Now that we have a [new](https://community.fibery.io/t/october-30-2025-share-entities-to-web-using-access-templates-new-names-for-access-levels-improved-file-fields-support-in-automations/9924) beautiful (and consistent!) set of Space access levels, we will gradually deprecate the legacy Contributor access: Quick reminder: Contributors can see and comment on all entities in the Space as well as create new ones. Additionally, Contributors can edit entities they have created or are assigned to. Contributor access is an echo of dark times when you couldn’t [share a Database](https://the.fibery.io/@public/User_Guide/Guide/Share-Database-342) or [automatically share Entities with …](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-with-assigned-People-327)