A renewable energy company manages confidential bidding proposals using a custom object named Partner_Bidding_Proposal__c. Executive leadership mandates that sales managers should only be able to view and edit bidding proposals owned by their direct reports. Users outside the owner's management hierarchy must have no access to these records unless explicitly shared. Additionally, the system administrator needs to ensure the baseline security configuration follows Salesforce best practices without creating unnecessary maintenance overhead. Which two administrative steps must the system administrator take to satisfy these security requirements? (Select two.)
- Set the Organization-Wide Default (OWD) for Partner_Bidding_Proposal__c to Private.Answer
- Ensure the 'Grant Access Using Hierarchies' checkbox remains selected on the custom object's sharing settings.Answer
- CDeselect the 'Grant Access Using Hierarchies' checkbox and create custom sharing rules for every manager.
- DModify user profiles to remove the 'Read' Object Permission on Partner_Bidding_Proposal__c for users outside the owner's hierarchy.
Answer
The correct configuration requires setting the Organization-Wide Default for Partner_Bidding_Proposal__c to Private and ensuring the 'Grant Access Using Hierarchies' setting is enabled.
To achieve a baseline where only owners and their manager hierarchy can access records, the Organization-Wide Default must be configured to Private. Concurrently, keeping 'Grant Access Using Hierarchies' enabled on the custom object allows managers above the owner in the role hierarchy to automatically inherit visibility and editing privileges.
Step-by-Step Solution
Key Concept
Organization-Wide Defaults (OWD) and Role Hierarchy Inheritance