Ursa Major Solar has a private sharing model on opportunities. Leadership has asked the administrator to create a new custom object that will track customer payment information and will link to the…

A lookup relationship does not automatically inherit sharing from the parent object; explicit sharing rules or other mechanisms would be needed.

A lookup relationship does not inherit sharing, and while criteria-based sharing rules could be used, a master-detail relationship is the most efficient and declarative way to achieve the desired sharing inheritance.

A master-detail relationship automatically inherits the sharing and security settings from the master (parent) record to the detail (child) record, meaning if a user has access to the opportunity, they will have access to the related payment information records. Profile permissions then control the specific CRUD operations users can perform on the child object once they have access to the record via the parent.

While a master-detail relationship ensures sharing inheritance, criteria-based sharing rules are not needed for the child object itself in this scenario, as its sharing is governed by the parent. Profile permissions define what actions a user can take on the record once they have access.