Hi team,
I want to implement the segregation of duties(security roles) in my model driven app. Lets say, If am trying to add 'basic user' role and 'system administrator' role to the same user then system should not allow that me to add the user and show some error. I am new to model driven apps. How can I implement this? Please share any documentation for reference. Thanks!
Yes. I started with plugin but can't able to achieve the output as expected. Any other solution is there that you can suggest me on this please?
Hi Fubar,
I just mentioned as 'basic user' and 'system administrator' as a example. But, actual roles are different. Let's say like this we created 2 roles 'creator' role and 'approver' roles. If we assign creator role to the user then they can't be approver. System should not allow to assign these 2 to one single user. How can I implement this?
You mentioned we can achieve this using Business Unit structure. Can you please share any documentation/YouTube reference ?
Are asking can you implement something when you assign a User to a Security Role? or how to stop once assigned?
For Assigning a Security role it could be done via a plugin.
Usually to implement separation and segregation of data,
a) System Administrator is not assigned to general users (only other way is to implement plugins on retrieve and retrievemultiple - I do not recommend this, and users with the System Administrator role can work around it if they really want to by disabling the plugin steps)
b) Implement a Business Unit Structure, and the BU Structure in combination with your Security Role Privilege levels and record ownership allows the separation and segmentation.
Dataverse Security Roles are always additive. Maybe you can implement this logic using plugins but it will affect all the environment and not only your model-driven app, however I do not suggest to go through this path.
mmbr1606
22
Super User 2025 Season 1
stampcoin
17
ankit_singhal
11
Super User 2025 Season 1