- Describe how security is structured in Salesforce.com.
- Explain how to determine what security permissions are required in order to complete an action in Salesforce.com.
- Describe profiles and their influence on security.
- Describe the significance of the Enable Enhanced Profile User Interface setting.
- List and describe the standard Salesforce profiles.
- Explain when to create a custom profile in Salesforce.com.
- Describe permission sets, and common use cases where they are appropriate.
- Describe the settings an administrator controls to conditionally allow or prevent user authentication.
- Describe how Organization-Wide Defaults (OWDs) influence security.
- Describe how the sharing button can be used to monitor record access and facilitate manual record sharing in Salesforce.com.
- Describe the significance of a user’s role and Grant Access Using Hierarchies on record security.
- Given a scenario, determine how to properly structure the role hierarchy.
- Describe the impact of role configuration on accessing records related to an account (contacts, cases, opportunities).
- Describe sharing rules, and when their usage is appropriate.
- Describe the different types of groups available in Salesforce and when their use is appropriate.
- Describe when to select Grant Access Using Hierarchies when configuring a public group.
- Describe a queue’s influence on security.
- Describe how access to list views, documents, email templates, and similar information is secured in Salesforce.com.
- Describe the permissions required to transfer (change ownership) a record in Salesforce.com.
- Describe delegated administration, and when its usage would be appropriate.
- Describe the significance of the View All and Modify All permissions in Salesforce.com.
- Security – Module Checkpoint
Overview of the Salesforce.com Role Hierarchy
Video Must 5m CertifiedOnDemand.com
Objectives for this Resource:
The role hierarchy provides a framework to structure access to records and other information in your organization. Various settings (sharing rules, groups, folder sharing criteria, etc.) rely heavily on roles to structure access to content.
It often helps to evaluate an org chart provided by human resources in order to create the role hierarchy structure in Salesforce. However, the role hierarchy in Salesforce must be designed based on access requirements and may ultimately vary significantly from an org chart provided by human resources.
Three examples provided by Salesforce are:
A user’s role sets the foundation for what records they can access.
Users are granted Full Access to records to records that they own, as well as records owned by owned by users in subordinate roles on objects where Grant Access Using Hierarchies is enabled.
Grant Access Using Hierarchies is always enabled for standard objects but can be disabled for custom objects.