Salesforce Standard Objects - Relationships

Below is the practical relationship breakdown in Salesforce— Lookup, Master-Detail, Junction. Let’s dive in.

1. Core objects → Lookup to Account (ownable, independent sharing)

• Contact → Account (lookup; Contact OWD can optionally be “Controlled by Parent”)
• Opportunity → Account (lookup, But Roll-Up Summary fields on Account that summarize Opportunities is applicable)
• Case → Account (lookup)
• Contract → Account (lookup)
• Order → Account (lookup)
• Asset → Account (lookup)
• Quote → Opportunity (lookup)
• Campaign stands alone (others point to it via junctions)

Takeaway: none of these are master-detail to each other.

2. Standard objects that behave like Master-Detail (detail has no owner; inherits sharing)

• OpportunityLineItem (Opportunity Product) → Opportunity
• QuoteLineItem → Quote
• OrderItem → Order
• PricebookEntry → Pricebook2 (also required link to Product2)
• CaseComment → Case
• EventRelation / TaskRelation → Event/Task (who it’s related to)
• WorkOrderLineItem → WorkOrder (Field Service)

These typically cascade-delete with the parent and don’t have their own sharing.

Note: Please remember, these aren’t real admin-created Master-Detail, but Salesforce designed them to behave like Master-Detail.

3. Junction / membership standard objects (two parents; “MD-like” behavior)

• CampaignMember (Campaign ↔ Lead/Contact)
• AccountTeamMember / OpportunityTeamMember / CaseTeamMember (Record ↔ User)
• AccountContactRelation (Account ↔ Contact, for indirect/extra relationships)
• ContentDocumentLink (File ↔ Any record)
• PermissionSetAssignment (User ↔ PermissionSet)
• GroupMember (Group ↔ User/Group)

They’re implemented with required lookups but behave like tightly coupled children (no independent ownership).

Add On — “Lookup vs Master-Detail” — the logic difference

The Benefit of understanding the relations

Understanding how standard objects connect — lookup, master-detail, and junction — lets you predict ownership, sharing, roll-ups, and cascade deletes so you’re never surprised by who can see or change a record.

It also helps you model data the “Salesforce way,” unlocking cleaner reports, safer automation, and features like ETM defaults that work exactly as intended.