Best Practices for Implementing Salesforce CRM - Cloud Experts

Using data access design patternsrepresentative grants read-write access on her opportunity to her APAC counterpart. For moreinformation on configuring manual sharing, see Help and Training.3. Account teams and sales Teams – Account teams give users the freedom to set default accountteams that include those employees who normally work together on an account. Users canautomatically add default account teams to all accounts. Sales teams can do the same whileworking on opportunities.4. Apex managed sharing – Apex managed sharing lets developers use Force.com code (Apex) toprogrammatically share custom objects. When you use Apex managed sharing to share a customobject, only users with the Modify All Data permission can add or change the sharing on thecustom object’s record. Also, the sharing access is maintained across record owner changes. Formore information on Apex managed sharing, see the Force.com Apex Code Developer’s Guide.You can use all these methods for the following sharing options: public groups, personal groups, users,roles, roles and subordinates, roles and internal subordinates, internal and portal subordinates, territories,and territories and subordinates. See Help and Training for definitions and usage recommendations.Sharing design considerationsSharing rules makes it possible to be flexible when assigning record access; be sure to review the followingconsiderations before adding sharing rules to your system.ConsiderationOpportunity and case access when accounts areprivateContact accessControlling access to associated child recordsApex sharing reasonsThis means that….When sharing an opportunity or case, users must have at least readaccess to the associated account (unless you’re sharing a case via acase team). If you also have privileges to share the account, usersare automatically given read access to the account. If you don’thave privileges to share the account, you must ask the accountowner to give the users read access.Contact access is not available when the organization-wide defaultfor contacts is set to Controlled by Parent.For sharing rules that specify access for associated object records,the given access level applies only to that sharing rule. Forexample, if an account sharing rule specifies Private as the accesslevel for associated contacts, a user may still have access toassociated contacts via other means, such as the organization-widedefaults, the “Modify All Data” or “View All Data” administrativepermission, or the “Modify All” or “View All” object permission.If using Apex sharing reasons, select a reason for the share so usersand administrators understand the source of the sharing. For moreinformation about sharing reasons, see Creating Apex SharingReasons.Territory Management: automate account accessTerritory Management (TM) is the final component of the data access model. TM is designed to automatehow large volumes of account records are assigned to users, thanks to declarative business rules triggeredby account record attributes such as zip code, industry, revenue, or another custom field relevant to yourbusiness.Why use TM?With TM, you immediately gain these benefits:• Assign account records to territories with declarative business rules and explicit assignments –Automate account record access to expand a private access model• Organization management – Manage complex and frequently changing sales organization structuresBEST PRACTICE 6