I want all team members to be able to view Contacts and Companies but restrict access to anything related to the Opportunity database and its fields, even if they are linked to other databases or views via relationships.
I tried setting up an Access Template, but I don’t see any options related to view-level permissions.
You have dbs (called Lead, Contact, Company, Opportunity and Meeting) and you have views (called Contacts, Companies, Sales Pipeline and Pipeline by Close Month).
The ability to see a sidebar view is determined by the permissions for the space it is in, but what a user sees when they click on a view depends upon the permissions for the database/entities being included in that view.
If you want users to be able to see the views in the sidebar, you have to grant them access to the CRM space, but this will mean granting them access to all the databases in that space.
If that is undesirable (because you don’t want them to see Opportunities, for example) then the database needs to be stored in some other space than the views.
Perhaps you should move the Opportunity database to a different space (where you don’t have views that need sharing with everyone).
Access templates are a mechanism for sharing specific entities, and related entities.
They have no effect on views.
So it’s possible that I might be able to see a view, but see nothing in that view because no entities (or dbs) have been shared with me OR
I might be able to see an entity (or entities) via search, or via a direct URL link to the ‘entity view’, but have no data views showing in my sidebar because the space has not been shared with me.
Thanks! I spent a few hours on this, repeatedly reviewing the guide, but made little to no progress.
Fibery’s permission and sharing mechanisms are far from intuitive. It feels like both its greatest strength and its biggest headache at the same time.
Your response about permissions also somewhat contradicts the feedback I’ve been getting in this thread
I initially planned to group databases under a single Space for the exact reason you mentioned—keeping databases together while using different Spaces and Views for more flexible access control.
I can’t imagine a scenario where someone managing a CRM, which naturally contains sensitive data, would want every regular user to have full visibility. The same applies to almost any type of Space—granting full control across the board just doesn’t make sense.
Access to Data is controlled via Space or Database
So in your specific case a solution can be this:
If a person should have restrictive access to CRM space, like see only Contacts and Companies, do not give them access to CRM space, but give access to these 2 databases only
Create a special space like CRM Public (or any better name), create Views for Contacts and Companies in this case and invite users to this space
As a result, full-access users will see CRM space and will not see CRM Public Space, and visa verse.
This is more complicated setup, since if you have a new user, you have to share databases with this user and also give her access to CRM Public space. But this is the only solution right now if you want to hide views.
To be honest, this is not a frequent request, but it is a very valid one. Maybe @antoniokov has better ideas?
Thanks for your response! Unfortunately, it doesn’t address my issue because I never granted the user access to the CRM or its databases. That’s why this situation has been so confusing and frustrating.
For now, I’ve restricted the CRM space so that only the creator has access. The Opportunity database within the CRM space has default permissions—nothing unusual there. However, the opportunities are being revealed in a different space, Software Development.
In what sense are Opportunities being revealed?
Can you provided a screenshot or video, from the point of view of a member who has no access to the CRM space (or its databases), which demonstrates them being able to see data from that space.
Note: the existence of a view (sidebar view or relation view) which is configured to show info from a specific database does not mean that everyone who can see that view can actually see all the entities that might qualify to be shown in this view.
The video does not show that a person is seeing data from the Opportunity database.
Yes, the relation view is visible, indicating that a relationship between the databases exists, but there is no data being revealed as far as I can see.