Organization-wide defaults and sharing for manufacturing records
Key Takeaway
Organization-wide defaults set the baseline record access for each object, separately for internal and external users. Keep a restrictive default and extend access with sharing tools, such as a sharing rule for internal users or a sharing set for Experience Cloud users.
An organization-wide default (OWD) sets the baseline level of access that users have to each other's records, object by object. Agentforce Manufacturing objects such as sales agreements, advanced account forecasts, account manager targets, and visits each have a recommended default. Each object gets one default for internal users and another for external users such as partners. You start from that baseline and open up access with sharing tools when the business needs more.
Organization-wide defaults and sharing
For most objects, you can set the OWD to "Private", "Public Read Only", or "Public Read/Write". Sharing rules, role hierarchies, and manual sharing extend access beyond that baseline.
Because sharing tools add access on top of the OWD, you don't need to loosen the default when some users need more. When an object's internal default is Private, keep the restrictive default and add a sharing rule for the users who need to see other users' records.
Northline Pumps changes the Internal Access setting for Sales Agreement from Public Read Only to Private, because the company wants tighter control over who sees agreements. Later, Mei on the pricing team needs to review agreements that other users own. The administrator could switch the default back to Public Read Only, but that would raise the baseline for every internal user. Instead, the administrator keeps Private and adds a sharing rule that gives the pricing team access. Mei now sees the agreements she needs, and the Private baseline stays in place.