In my org, Account object have OWD as public read only. And I have a custom object C1 which is a child of Account (Master-Detail Relationship).

If a new record is created for C1, it gets saved at the Account which is in the top of Account Hierarchy.

The problem is, I have sharing rules on Account based on the Field 'Sales Region'.

The user in one region has only Read access on the records in another region.

So, if I have a record for Custom object C1, whose Parent is A1 (Account) which is in one region e.g. Asia, while A1's parent A2's sales region is another e.g Europe. If I try to create an attachment or Notes for a record of C1 which is saved at A2, then I am getting Insufficient previliges Error because the user don't have access to A2.

Please suggest any solution to resolve this. TIA

  • If even a single user should not have access to a record then the owd should be private. Rules are to grant access not restrict them – Eric Nov 8 '16 at 6:34
  • In this case, the users belongs to one Account region can see the records in that region only. – Seshu Paturu Nov 8 '16 at 7:30
  • right. Then owd should be private – Eric Nov 8 '16 at 11:41
  • Thanks @Eric and I have a question : If I make Account's OWD as Private, can other users able to have Read access on Accounts belong to the same region? – Seshu Paturu Nov 9 '16 at 6:42
  • Suggest you read up on Salesforce security. The golden rule is "OWD is used to restrict not grant access. Sharing is used to grant access" also, if the answer to the question should any single user NOT be able to see a record is true then the OWD should be private. To answer your question, yes, you grant them access by Sharing settings. If you make everything Public read, you CANNOT make the security more strict than that as you cannot take away access with anything except by using OWD. – Eric Nov 9 '16 at 6:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.