Use case for the feature of Record ownership across Business Unit
#configuration, #security, #permission, #crossBU
Last updated
#configuration, #security, #permission, #crossBU
Last updated
Today, I would like to share an existing configuration on the Power Platform Admin Center. This feature is regarding record ownership impact on the permission of the user.
Firstly, let's see my scenarios as picture here
User A is working for 2 BU: BU1 and BU2. However, as my scenario flows, this User was assigned different roles for each BU.
Go to the Power Platform Admin Center > select environment > into the Feature area, turning on the feature "Record ownership across Business Unit".
Once enabled:
Allows you to assign security roles from different business units to a user.
Users can have different roles for each BU assigned.
To assign security role for a User for different BUs, you go to the Power Platform Admin Center. After that, go to User + permission area >> click User >> then select specified User (ex: TEST HS) and click Manage security role, then select BU and assign roles for the user.
Activating the Record ownership across BU feature resulted in the Business Unit field being enabled, whereas it was previously disabled.
Please review the test security roles listed below. Following that, I will present the testing results for this feature. My test role: Salesperson-X and Salesperson-Y
First, I logged in by user Admin and checked the data of Account entity as bellow.
Total account records: 33
Accounts of BU1: 04
Accounts of BU2: 5
Now, my expectation when log-in by user TEST HS:
Can see 9 Accounts of Child BU 1 & Child BU 2
Can Edit Account of Child BU 1
Cannot Edit Account of Child BU 2
... and then my testing Result
Open the account record of each BU for permission testing
I will now reveal a concealed setting that activates the Owning Business Unit field on the form for all entities. Once this field is enabled, users can create an Account record and then assign it to a different Business Unit to which they are assigned.
Before enabling this hidden setting - the field Owning Business Unit was set Read-Only. So, the user does not assign this record to a different BU.
After that, we will enable the hidden setting of the Environment Database Setting. You must install a solution - OrgDBSettings tool at the link.
After installation, navigate to the solution within the configuration area and set the 'RecomputeOwnershipAcrossBusinessUnits' setting to 'true'. This will enable the 'Owning Business Unit' field to be modified and the user can assign account records to a different BU.
Let checking.....
Hoping well and thank you! [NTD]yns.Asia
Tadaaaa... That's all today.
