Q: 11
The finance team at Universal Containers usually does not have access to account and contact records. A finance analyst was temporarily given opportunity access for a big deal to help with tax calculation. However, she can now also access account and contact records. What is causing this issue?
Options
Discussion
Option A
Probably C. If Contacts have OWD set as "Controlled by Parent" and she got implicit access to Account through Opportunity, that could explain why she's seeing Contacts too. But I'm not sure if this would cover the Account access directly-seems like a bit of a Salesforce nuance. Anyone else run into edge cases with Contact visibility after temporary Opportunity sharing?
A . Implicit sharing from Opportunity is the reason, unless Account OWD was public which would override it.
Yeah, it's A since opportunity access grants implicit read-only access to the parent account. That's core Salesforce sharing behavior. Contacts might be visible if they're controlled by parent, but the main trigger here is that implicit share via Opportunity. Pretty sure this only matters if OWD on Account is Private though, otherwise it wouldn't be noticeable. Agree?
This depends on whether the question is asking about best practice or what actually happens out-of-the-box in Salesforce. If account OWD was set to Private, would this still occur?
Had something like this in a mock, it's A.
A here, implicit sharing from the Opportunity to its Account is classic Salesforce. Saw a similar point on some practice exams and the official guide. If you want to really master these scenarios, check both guides and hands-on org labs. Pretty sure on this but shout if you think another option fits better.
Not C, it's A. Opportunity access gives implicit read-only on the related Account, so that's why the finance analyst sees those records now. Contact access would only cascade if they're set to "Controlled by Parent" but the root cause is really that child-to-parent implicit sharing for Accounts. Pretty standard setup in Salesforce permissions.
A. that's implicit sharing from Opportunity to Account. Pretty sure that's standard Salesforce behavior when you get access to a child object.
Be respectful. No spam.