You’re offline. This is a read only version of the page.
I have a model-driven app and would like to restrict the users from seeing each others data. Now I have already managed to do this based on the entity by assigning a security role for each table, but I would also like the app to behave in such a way that the user cannot see anything else than the table and the group it belongs to in the left hand navigation, so that he/she cannot click on the other tables. Below is a screenshot of how it is now, when the user has navigated to a table he/she does not have access to.
Is this possible to do by assigning some kind of securty role to the user?
Since the app is supposed to be a data input app, where the different users can login and they would see their tables and then import an excel to that table, I am considering also if its easier to create multiple model-driven apps for each user and table in order to get only the table(s) the user has access to to be shown in the navigation?
Thanks for the answer, much appreciated!
No, it still seems to show every table in the navigation. Might however be something with the browser if it should work by simply giving the user a role with access to only one table and it shouldn't show any other tables in the navigation.
But we have tried a different approach were we have created multiple model-driven apps for different tables, and then assigned the role and it seems to solve the issue for us, since it's really the same if the tables are in one app or in multiple apps, since the customers only use one table each and they would still need a per app license if we went on only one app instead of many different apps. Also it might be easier to handle the different security roles if the user only has access to the app where the table is.
@Anonymous
Did you manage to resolve this issue?
Could it be a cache? Can you please try to log in with an Incognito/InPrivate browsing to see if the user is still able to see the table that they do not have Read access in the left-hand navigation (sitemap)?
@LinnZawWin yes, all the tables were added as Dataverse tables and not as URL:s. But after creating a security role and giving permissions only to one of those tables, the user is still able to see the tables on the left hand navigation and once he clicks on a table he does not have access to it gives the error that he does not have permission to the content, which of course is fine, but he can still see and choose all the tables on the left hand navigation.
@Anonymous
By default, the model-driven app would only show the tables that the user has access to in the left-hand navigation. In the following app of mine, the Test user is not able to see the red-highlighted tables that the Admin user can see.
Can you please confirm if you added those tables to the left-hand navigation (sitemap) by adding those as a Dataverse table page and NOT as a URL?
#1
Michael E. Gernaey
11
Super User 2025 Season 1
#2
bscarlavai33
5
Super User 2025 Season 1
#3
getsplash
2
Share
Report
All responses (
Answers (
