Skip to main content
We have a new sales team that is being onboarded into an already established org that's being used to manage opportunities for a single business unit. This new sales team will operate autonomously from the rest of the org as their opportunities would be considered part of a 2nd business unit. At the same time, it's ok that everyone see each other's opportunities.

 

I'm currently running a private read only opportunity sharing model and looking for some guidance on the least disruptive way to setup this new team so users wouldn't need to take into account this other business unit when generating reports, for example. I had been going down the path of a unique record type and profile for this business unit but don't want other users to take into account that criteria when generating reports (i.e. all opportunities EXCEPT this new business unit/record type).

 

Recommendations?
1 respuesta
  1. 6 jun 2018, 8:54
    Hi Donny,

     

    You can accomplish this either with sharing settings or divisions.

     

    Sharing Settings: Set the account and opportunity objects to private and use sharing rules to open up read and/or edit access to appropriate records for each business unit. Users will only see records they have at least read permission on in reports. Be careful of implicit sharing, though - if both business units need access to the same set of accounts, they will also get access to all opportunities related to those accounts

     

    Divisions: You can contact Salesforce to enable divisions, which will allowyou to segment your org by business unit. Reports and list views will then include a standard filter to select the division. Users will have access to all records, but reports will function by default as if they didn't. A caveat, however, is that the division of an account drives the division of child records, so you may have a similar issue to inherent sharing above if there is overlap between account access.
0/9000