Salesforce Platform App Builder Certification Training - Grant Access Using Hierarchies

The video tutorial explains how role hierarchies in Salesforce automatically grant record access to users higher in the hierarchy, which can be disabled. It discusses the impact of parent-child relationships on access and security, particularly in master-detail relationships. The tutorial also covers organizational-wide defaults (OWD) and how changing them can affect manual sharing. It highlights the permissions like 'view all' and 'modify all' and their implications, as well as limitations on certain objects like the solution object.

What is the default behavior of role hierarchies in Salesforce?

• They only apply to custom objects.

• They require manual configuration for each user.

• They automatically grant record access to users above the record owner.

• They restrict access to records for users below the record owner.

How does a child record in a master-detail relationship inherit its access settings?

• It has independent access settings from the parent.

• It inherits the organizational-wide default from the parent.

• It can be edited independently of the parent.

• It is always set to public read-only.

What happens when you change the OWD from private to public?

• It automatically deletes all records.

• It potentially deletes manual sharing that is no longer needed.

• It restricts access to all users.

• It has no effect on existing records.

Which object in Salesforce has a fixed OWD setting that cannot be changed?

• Contact object

• Custom object

• Account object

• Solution object

What permissions allow users to view and modify all records, regardless of ownership?

• Edit and Delete permissions

• Custom Object permissions

• View All and Modify All permissions

• Read and Write permissions