Custom Visibility Code

Question

Hi Everyone, 
 Does anyone know if it's possible to have custom visibility code that will show a module results in the sub panels under a record but not allow the user to open that result or view the result in a report unless that have access to the team associated with the result? Hopefully the example below makes sense. 
 Example: 
 Organization #1: Opportunity 1 - Blue Team Opportunity 2 - Red Team 
 In the example above, I would want to open up organization #1 and see both opportunities below it. However if I am only on Red team then I should not be able to open up Opportunity 1 as it is assigned to Blue team or see it in a report. 
 Thanks in advance!

Dan Petersen · Answer

Hi Dan, 
 Since my Integros team has experience of extending the Roles permission matrix with additional columns (including introducing Create end separating it from Edit) along with rebuilding the OOTB security model for the sake of speeding up cascade updates of hundreds of thousands of records for on-prem customers - to avoid updates of Team for very each the subordinate records whenever the parent Account gets new AssignedTo and Team - I would strongly recommend avoiding core security adjustments until it is critical for Sugar adoption and renewal. If the purpose is to help users with their business target while keeping team restrictions in place and OOTB, let me suggest a simple no-code solution that is implemented in 2 steps: 1. Add a new custom module "Opps D igest" with Studio and relate it to Accounts as many-to-one. 2. Configure logic that would refresh the OppDigest records - with data necessary and sufficient for business decision - no extra Opp info. For example, show in OppDigest module all open Opps regardless of the team and sales rep the Opp is assigned to. Therefore, users could benefit from the information available for decision making while having team-restricted access to Opps via both interface and reports. Interface for Will from BLUE_TEAM on the left and for Sarah from RED_TEAM on the right: 
 The example implementation: step 1 - zip provided by Studio no-code tool - the OppDigest module (only please add relation to accounts manually via Studio) OppDigestModule.zip step 2 - zip generated by Logic Builder ( https://logicbuilder.integroscrm.com ) no-code tool - the logic to create/update/delete OppDigest record automatically on Opp is updated LogicThatRefreshesOppDigest.zip Please feel free to use the solution. Let me know if any questions or need some logic adjustments to make the example work for your company as prod In case you are curious about the logic configuration for create/update/delete OppDigest, here is the flowchart (please zoom in an follow the white line to read)