# Hiding Unwanted Relationship Fields from Users Without Access **URL:** \ **Category:** Get Help\ **Tags:** permissions\ **Created:** [March 8, 2025, 3:47am UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405 "2025-03-08T03:47:54Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 8, 2025, 3:47am UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405/1 "2025-03-08T03:47:54Z")
I have a **Story** database in a **Software Development** space, with a relational field linking to our **Company** database, which lives in the **CRM** space. I’ve tried everything to completely hide **Opportunities** , but I can’t seem to remove them entirely. While I’ve managed to hide the actual entities, the board layout still appears—it’s empty, but it’s still there. This test user has **no access to the CRM space** , yet the board remains visible. I want them to have a **simple view of the company** without seeing anything related to sales. Is there a way to hide it completely? ---
**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:** [March 8, 2025, 8:20am UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405/2 "2025-03-08T08:20:49Z")
If you click on the triple dots in the top right corner of the relation view, you will have the option to hide it. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [March 8, 2025, 8:26am UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405/3 "2025-03-08T08:26:45Z")
Have you looked into [multiple entity views](https://the.fibery.io/@public/search/HTbXS#User_Guide/Guide/Multiple-Entity-Views-335)? You can create different views of an entity so that a field can be hidden in one view but still present in another. Users can switch between them, but it’s helpful to allow users to be able to focus on only the elements that are relevant to them. ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 9, 2025, 1:18am UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405/4 "2025-03-09T01:18:42Z")
Multiple views wouldn’t solve this issue. I don’t want this type of user to see the data at all. They don’t have access to the CRM space and work exclusively within the Software Development space. I only want them to see the **contact and company attached to the Story** —but without the ability to click into them and access other CRM data. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [March 10, 2025, 5:37am UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405/5 "2025-03-10T05:37:58Z")
Currently, I think the only way to go about completely hiding fields from some and not others is to have the fields hidden from all entity views. Then for those who need the data, they have a view (like table, for example) within their Space that contains those fields. ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 10, 2025, 4:24pm UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405/6 "2025-03-10T16:24:30Z")
Thanks! Unfortunately, this is the best approach for now. I’ve split our CRM into two Spaces: **CRM** and **Sales CRM**. ![CleanShot 2025-03-10 at 12.16.37](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a1b952babb72156209193c89a3abc225d9c580f9.png) **CRM Databases** : Company, Contact **CRM Sales Databases** : Lead, Opportunity This resolves the **permission issues** I was facing, but unfortunately, it introduces some **annoying nuances** that I hope will be addressed as Fibery evolves. For example, while the **Company view** is super clean, there’s no way to access a **more detailed view** without exposing additional information. I can create a view that breaks down opportunities by company, status, and other criteria, which is great. However, I can’t create a comprehensive view of a single company that pulls in details from both Spaces. Ideally, a user with the right permissions should be able to see everything related to a specific company in one place. ---
**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:** [March 10, 2025, 4:55pm UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405/7 "2025-03-10T16:55:48Z")
The presence of a relationship between two databases does not mean that everyone who can access the entity view of an item in one database can automatically see the linked items in the related database. For example, imagine a user has Viewer level access to Database A but no access to a related Database B. When they open an entity of type A, they will see that it has _the possibility_ of being linked to entities of type B, but they will not be able to see anything from database B. They will not know what entities (if any) of type B are linked to the type A entity they are looking at. This is a fundamental principle. Irrespective of what view you are looking at (entity view, table view, board view) you will only see entities that you have access to. However, databases live in spaces, and so if you grant access to a space (in order for someone to see the views that live in the space) you are automatically granting access to all dbs in that space. If this is not desirable, then the views and the databases need to be ‘decoupled’, by having them live in separate spaces. In your case, it indeed sounds like it makes sense to have a space for Companies and Contacts, and a separate space for Leads and Opportunities. This means some people can be granted access to only the former space, and some people can have access to both spaces. But the permissions are independent of views. So you could, for example, create a table view of Opportunities in the space that contains the Companies and Contacts databases, without worrying about any data being exposed. Anyone who didn’t have access to the Opportunities database would not see any records in that view. So to be clear, with respect to this: > [@Edan](#): > > I can’t create a comprehensive view of a single company that pulls in details from both Spaces. Ideally, a user with the right permissions should be able to see everything related to a specific company in one place. there is no reason why Companies cannot be related to Leads and Opportunities. You will not expose data from these databases by creating a relationship. On the Company entity view, the Opportunities relation field will not reveal anything to someone who does not have access to the Opportunities database But it will show linked Opportunities to whose users who do have access to the Opportunities db, thus allowing them to see everything related to a company in one place. If that is not what you’re getting at, perhaps I am missing something, and you want to clarify exactly what you would like to see when you write “see everything related to a specific company in one place.” ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [March 12, 2025, 10:57am UTC](https://community.fibery.io/t/hiding-unwanted-relationship-fields-from-users-without-access/8405/8 "2025-03-12T10:57:17Z")
Are there three threads about this? Lol, looks like you already found yourway to a Sales space. Yay! > [@Edan](#): > > However, I can’t create a comprehensive view of a single company that pulls in details from both Spaces. Why not?