Dataverse Record Level Security in Power Apps

00:00 - Intro
00:55 - Enable Business Unit Ownership
01:39 - Create Business Units
02:15 - Create Security Role
04:04 - Assign Security Role
05:59 - Create Business rule
10:26 - Final Demo

The scenario here is to enable row level security within the concepts of Dataverse. Important to note, this can be applied to Canvas or Model-driven apps.

For example:
I have a Sale Commission table which is connected to a Model-Driven App. One of the columns is a choice called Store.

To do this functionality we will be using the following:
- Business units
- Security role
- Dataverse table
- Business rule
- And more..
::---------------------Documentation---------------------::
Record Ownership in Modernized Business Units

Security in Microsoft Dataverse

[anbu]

Thanks for the video; it was really useful. I just wanted to add two points related to this. One is that if you deploy this BR to other environments, the BR would fail to deploy/activate because of invalid reference due to hard coded BU GUIDs in the BR. The other point is that if someone assigns a record manually using the Assign button in the command bar, the record will most likely move out of that business unit and onto the new owner's unit.

[kannankarmegam-bne]

Fantastic demo. MVPs really suck at explaining this concept.. you nailed it.

[pramodagarwal]

This Video was very informative. Make more videos on Business Rules and Dataverse Table relationships

[davediguer]

Hello - thanks for putting together this video. This was very helpful. Looking at the fields in a Dataverse table i see there is Owning Business Unit, Owning Team, and Owning User. I will also do some research into the Owning Team and Owning User fields to see how they can be used. Any chance you want to make a video on those ....😁

[radhashroff]

Thank you for this video! Is there a way we can set more than one teams as owning team of the record?

[martinnoah]

Why do you use the choice field and not just have the Owning BU field on the form?

[e-polk]

This was very helpful. I changed a user to a different business unit and updated her security role to Parent Child Business Units level on all my custom tables. She can no longer see the records on the Lookup tables that someone else entered in the Original Business Unit. Can you tell me what I might have done wrong?

[headflask]

How would this work with Power Pages and the Contact List? I would want users from one client to only see their client records. Some users (internal or consultants) could see more than just the one client's records. Right now I have been trying table permissions per Account but that doesn't allow viewing more than one account at a time. Looks like permissions are linked to a person through Contacts or Accounts.

[ronn_zw]

Thanks for sharing. Maybe expand it to have a global role that will see all the records.

[stabiloboss]

hi flow alt delete. really appreciate the video! But i ran into a problem that others might have aswell.

My problem is that my new users, being added to the business units in the way you've said, cant view the table of interest in dataverse.
Instead, an error message appears: 'We couldn't load your data. Please try again later'.

What my general background is:
- I am an admin in a dataverse development environment. In this environment I created a table in which i need row level security.
- i created a new test user, and have just added it to this development environment in hope it will enable the user to see the table.
- and i have followed the steps in this video to implement record level security in this table, and have assigned the new test user to a 'child' business unit.

I have been stuck on this for ages! Let me know a solution (anyone)