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

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!

OriginalPostID-155229

OriginalPostID-155229

  Discussion posts and replies are publicly visible

Parents
  • stefanh791 - we are aware of that approach, however in some of our processes that could lead to creation of tens of thousands of unique groups over the course of a year, which would create performance issues for users who are frequent participants from what I have read. Many of my processes currently use process instance security to give access to both admin groups and and initiator, but also to every person who has participated in the review/approval process. There doesn't seem to be any good way to replicate this behavior in record based design.
Reply
  • stefanh791 - we are aware of that approach, however in some of our processes that could lead to creation of tens of thousands of unique groups over the course of a year, which would create performance issues for users who are frequent participants from what I have read. Many of my processes currently use process instance security to give access to both admin groups and and initiator, but also to every person who has participated in the review/approval process. There doesn't seem to be any good way to replicate this behavior in record based design.
Children
No Data