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
  • 0
    Certified Lead Developer
    Good - though keep in mind that one of the main points I was making is that you'll have the ability to do your group comparison within the Default Filter expression (instead of worrying about the "Viewer Group" setting in the record setting itself); you should be able to utilize loggedinuser() and check if the user is a group of the permission group(s) you want. The advantage here is that it gives you intricate control as well as ease of editing in the future without having to worry about messing with the viewer group setting on the record page.
Reply
  • 0
    Certified Lead Developer
    Good - though keep in mind that one of the main points I was making is that you'll have the ability to do your group comparison within the Default Filter expression (instead of worrying about the "Viewer Group" setting in the record setting itself); you should be able to utilize loggedinuser() and check if the user is a group of the permission group(s) you want. The advantage here is that it gives you intricate control as well as ease of editing in the future without having to worry about messing with the viewer group setting on the record page.
Children
No Data