Custom Visibility Code

hi Dan,

Could you clarify the business purpose by describing the use case from the business perspective? That might help with the  implementation options

Do you need, e.g. Blue team members to be aware of the Opp managed by the Red team so that not compete with the Red team for the same Customer?

What info specifically should help Blue team to decide not to create the Opp? E. G. product name/product category, some specific Opp contact involved, else?

Hi Dmytro,

Basically exactly what you said. We need all teams to see that their are opportunities under an organization, but not allow them to click into the record if they are not part of the opportunities team (we should not be competing against the teams). Technically we could hide a few fields within the opportunity from unrelated teams, but it is my understand that if someone ran a report then the hidden fields would show on that given report.

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 Digest"  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)

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 Digest"  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)