At the moment, it seems like the current permission levels could be represented as follows: Level View entities Edit entities assigned to me Edit entities Configure views Configure types No access Viewer Y Contributor Y Y Editor Y Y Y Creator Y Y Y Y Y I think there…

Yes. Unfortunately, that is the case. It is not currently possible to restrict a user from seeing entities that are the same type as the ones he/she is contributor/assigned to without siloing the information, and that loses the advantages of connectivity :frowning: But soon it will be possible …

Thanks again for reply, but this is actually my worst nightmare. I am discovering other problems: I am not able to create multiple copies of my application, perhaps I am stupid but going in new app/templates it shows the “goto app” button and it sends me to the existing one now people will have t…

[image] mgiammarco: I am not able to create multiple copies of my application ‘ Clone/Duplicate App Type - #3 by Matt_Blais ’ [image] mgiammarco: now people will have to look in two (or three) different places to see their tasks You can still create views that display entities that come…

[image] Chr1sG: It’s far from ideal, but until the new permissions model is rolled, out, it is the only way, unless maybe you can live with people having view but not edit access for entities they are not assigned to? Absolutely not these are different customers and they must not see products…

Then you would have to use separate apps for each customer.

I assume this limitation will be addressed by the planned per-entity permission model?

Is there even a vague estimate of when Entity-Level Permissions might be implemented? It is a necessary feature for my use case (and many others).

[image] Chr1sG: Then you would have to use separate apps for each customer. If our goal is to limit “Customer” user access (today) to specific “Product” entities, is this a viable workaround: Create a separate “Customer Xyz” App for each customer, which we will try to use to allow specific …

[image] Matt_Blais: is this a viable workaround It certainly is a viable workaround, and it might even be possible to make it less labour intensive with some automations (like, create a ‘shadow product’ every time a product is assigned to a particular customer). However, assuming that your i…

Permissions - entities vs views

Ideas & Features

mdubakov August 17, 2022, 9:22am 33

This is in plans and we call it Entity-level permissions. We are going to start implementation soon. You can check some details here.

Topic		Replies	Views
[DONE] Entity-level permissions Ideas & Features permissions , sharing	114	6254	October 18, 2024
Nov 16, 2023 / 🔒 Entity permissions (experimental) Changelog	60	2167	June 18, 2024
Feature Request: Share Space but restrict entity views Ideas & Features permissions	53	718	March 29, 2025
September 18, 2025 / ⚔️ Specify which Entity View to open based on some field value Changelog	33	849	March 5, 2026
October 2, 2025 / 🥗 Bunch of usability improvements Changelog	32	656	March 5, 2026

Permissions - entities vs views

Related topics