How is everyone handling record security, when requirements require dynamic visi

Chris over 8 years ago

How is everyone handling record security, when requirements require dynamic visibility? For instance, we require records for an application to be visible for all application administrators and also to the process initiator (initiator should only see the record for the process isntance they have initiated). Sometimes, company divisional views are necessary as well - divisional administrators should only see records for their specific division. With nearly 40 applications in production, we do not want to have 3+ records for each application. Just wondering if anyone has experience with similar situations. Thanks!

Discussion posts and replies are publicly visible

Parents

0 Chris over 8 years ago

In this case the end users (for which the expression will be evaluating under), do not have permissions to see group "Developers", for example. So if that group is in a constant (which would be better practice for sure), we would still have to run doesUserBelongToGroup(), which AFAIK requires admin permissions - resulting in an error for end users. Basically the text method is a work-around so the system can decide if an end user is in a group they cannot see under their context.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Chris over 8 years ago

In this case the end users (for which the expression will be evaluating under), do not have permissions to see group "Developers", for example. So if that group is in a constant (which would be better practice for sure), we would still have to run doesUserBelongToGroup(), which AFAIK requires admin permissions - resulting in an error for end users. Basically the text method is a work-around so the system can decide if an end user is in a group they cannot see under their context.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data