I am currently admin for an org which uses installed packages that are essential to business processes. As a caveat to having these packages I must keep my Sharing Settings to Public Read/Write for certain objects.
With these settings our Sales Rep users are able to see all records of the public read/write objects.
Is there a way to create groupings of records I can assign to a Role and restrict all other records of the same type without changing the Orgs Sharing Settings?
Thank in advance for your help.
Extension: The app we need Public Read/Write permissions for is Mailchimp 4 Salesforce (MC4SF) which creates Leads in Salesforce after a sync.
I have had a reply from MC4SF: "We do require those Sharing Settings to be set to "Public Read/Write" for Leads, Contacts and Accounts. Due to the way the MailChimp for Salesforce integration interacts with Salesforce, without those public settings, we'd be unable to create new Leads from MailChimp subscribers and we may run into issues with syncing MailChimp subscribers to existing Contacts/Leads, querying Leads/Contacts to add them to MailChimp lists, specific groups or segments, or even associating MailChimp campaign activity (opens, clicks, etc) with Contacts/Leads in Salesforce."
Ideally we want to keep our Sharing Settings locked down and then open up access using Territory Management and Role Hierarchy. I also am looking for confirmation (in salesforce documentation) of how installed packages are affected by sharing settings in an org. I have searched and found nothing that relates them.