Author: zeusexam

High-volume community users High-volume community users do not have roles, which removes any performance degradation related to sharing calculations with external users: they are not affected by the number of roles that are selected in the Communities Settings page. The related user licenses are Customer Community, High Volume Customer Portal, and Authenticated Website. But how…

Sharing within Salesforce communities Before closing this chapter, a few words should be said on how sharing is handled in communities. You should already be aware of what Salesforce communities are, but let’s provide a brief summary anyway. Salesforce communities are a way to allow external people to interact and collaborate with your business processes….

From the Opportunity Territory Assignment section, you can enable a more detailed filter when setting up territory management for Opportunities. The default OppTerrAssignDefaultLogicFilter Apex class can be found in the documentation (see https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_interface_TerritoryMgmt_OpportunityTerritory2AssignmentFilter.htm) and is out of scope for this book (ask a developer to help you with the setup). Each territory has its own…

Enterprise territory management The last way to share records is by aligning your company’s sales territories hierarchy. This kind of sharing model is applied to account sharing and related opportunities. At the time of writing, there are currently two different kinds of territory management: For the scope of the Salesforce Advanced Administrator certification, we’ll describe…

Some considerations about sharing There are some peculiarities and exceptions regarding the sharing model that you should be aware of. The following are the peculiarities and exceptions regarding role hierarchy-based sharing: Regarding object deletion, a record can only be deleted by its owner, administrator, users above them in the hierarchy, or any user that has…

Team sharing You can define account, opportunity, and case teams to ease collaboration on those objects and increase access levels for specific users in the team. Account teams An account team groups a number of users that work together to manage a given account record. To enable account teams, click on Setup | Feature Settings…

Role hierarchies With role hierarchies, users can have access to records that are owned by or have been shared with users below their hierarchy. In a few words, the CEO (the person with the highest role) can see any record owned by any user, while the Sales Manager can see records that are owned by…

The Salesforce sharing model Once you have selected which objects and fields a user can have CRUD access too, you need to know how to control record-level access. We can do this using Salesforce’s sharing settings. OWD sharing To define the Organization-Wide Defaults sharing settings, go to Setup | Security | Sharing Settings: A selection…

Object-Level Security (OLS) The first level of access type is Object-Level Security (OLS), as we saw previously on the profile edit page: These kinds of operations are usually referred to as CRUD operations: Some of them respect sharing configurations while some do not: View All and Modify All work like the View All Data and…

Permission sets Permission sets are, as the term suggests, a collection of permissions or settings that give users access to specific platform features/functions. Permission sets are used to extend application feature access to users without changing their profiles. Every setting you can apply to permission sets is also found on profiles (but not vice versa)….