![]() ![]() ![]() In the Sharing Rules area, click New and give your rule a label.Choosing an object in this drop-down list allows you to focus in on the org-wide defaults and sharing rules for a single object at a time rather than looking at all of them in a long page-a useful thing if you've got a large org with multiple custom objects. In the Manage sharing settings for drop-down list, choose the object for which to create the sharing rule. ![]() This is the same page used to define org-wide defaults. From Setup, in the Quick Find box, enter Sharing Settings, and then select Sharing Settings.In this group, we add the SW Dev Manager, Director Product Management, and Director QA roles, and the role and subordinates of the Recruiting Manager. Since both recruiters and hiring managers need read and update access to job applications and reviews, we can define a public group called Reviewers that includes both recruiters and hiring managers. The good news is that we can cover these objects in a single group because the Review object is on the detail side of a master-detail relationship, so it inherits the sharing settings we apply to the Job Application object. Looking at the required permissions that we want to implement for our Recruiting app, there are just two objects that need a public group for their sharing rules: Job Application and Review. ![]() Once you’ve defined your group, you can use it to define sharing rules.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |