Sharing: Beyond the Thanksgiving Feast

In a few days, Americans will gather around tables with friends and family and share a feast. It will be a time of reflection and gratitude for the blessing brought throughout the year. There will be lots of sharing: memories, traditional food, space on the couch, and maybe a game of football. Thanksgiving is a tradition that fills our hearts and bellies!

But sharing goes beyond the Thanksgiving Feast. When it comes to Salesforce, one of the key security features is Sharing Rules. (If I tricked you into thinking this “techy” post was more about how to share our love for Salesforce and each other, jump over to this post where I talk about the BAM movement.)

What Must You Know About Sharing Rules?

  • Sharing rules are used to share records that users do not own
  • You can define up to 300 user sharing rules
  • You can use sharing rules with groups
  • Organization-wide defaults are set (by default) to either Public Read Only or Private
  • You share to public groups or roles, which makes them less restrictive than OWD’s for objects.

Just like at Thanksgiving, sharing isn’t always easy – but it also isn’t difficult. Say that you have a “Recipe” object but you don’t want to share your signature pecan pie recipe with everyone that can see the recipe object. You will want to use a sharing rule to give access to your siblings but leave it so nosey Aunt Mo can’t figure it out and brag that it is her own.

In a sales org, I use sharing rules to allow regional Territory Managers to see Opportunities in their global region (ie UK) with a UK TM’s group. They have read-only access but can see all the win/loss details and learn from each other.

Hopefully you learned something new through this post, now off to pick up that pumpkin ice cream pie from my local ice cream shop (I promise not to brag that I made it)! Below, share your favorite way to use sharing rules and your favorite Thanksgiving dish – no recipes requested!


Leave a Reply

Your email address will not be published. Required fields are marked *