Drill Back Security for Confidential Data

[aricgresko]

Hey all - does anyone know the best practice to securitize the drill back functionality based on Entity (or other group) access?  My use case is that we have users who can see entire company financials (actuals and planning) but should not be able to drill back to the People Planning registers unless they meet a certain criteria (in a specific security group and have a specific entity group access).  
Thanks for any assistance!

[NicolasArgente]

Hi @aricgresko 
Drill back security can be customized. But first, there is not such thing as a drill back security out of the box, you will need to customize the drill back to show or not depending on the user group. You would do that in the connector business rule and more precisely under the "Case is = ConnectorActionTypes.GetDrillBackTypes".
You could also add in "ConnectorActionTypes.GetDrillBack" there something like "if the user is in this group, then run that query otherwise run that other one".
But as you can see, it is all with coding. There is no such thing as a drop down list where you would select the security group.
Hope it helps

[aricgresko]

I wanted to close the loop on this that writing custom coding within the Case Is = ConnectorActionTypes.GetDrillBack was what we needed to get the job done.  Thanks for pointing me in the right direction @NicolasArgente !

[NicolasArgente]

You are most welcome  @aricgresko 🙂

[aricgresko]

Thanks Nic.  I have begun down that path with BRApi.Security.Authorization.IsUserInGroup(si, "GroupName") and that does work at a basic level.  However, I need this to be more conditional, looking at a user's Write security access vs. the Entity they are drilling back on.  Initially seems like something to pass a member list into but was having some issues with getting that to work.