Q: 13
The sales managers at Universal Containers requested their teams to define each user's role on their
accounts in order to provide an easy way to establish accountability and collaboration. Sales
managers also requested that sales associates should only get the following permissions: 1. Read
access to the accounts. 2. Read access to cases related to the accounts. 3. No access to deals related
to the accounts.
The sales associates may be granted access to opportunities when needed.
Assuming the overall sharing model of the organization is Private and no sharing rules
are configured on the Account object, how should an architect achieve these requirements?
Options
Discussion
A . Account teams let you control specific access to Accounts plus related Cases and Opportunities for each user, matching the scenario. You can fine-tune read-only or no access as needed. Saw similar logic in the official guide, but open if someone disagrees.
Option A is the one I remember seeing in practice exams and fits here. Account Teams let you set those varying permissions for each user on each account, including blocking sales associates from opportunities unless explicit. Pretty sure that's what the question wants, unless I'm missing a nuanced requirement.
B
A or B. If "may be granted" means ad hoc access, Account Teams (A) handle that, but if you want to always block opportunity visibility without exception B could edge out. Depends how much flexibility they want.
A imo , but not 100 percent sure since "may be granted" could mean you want more flexibility than just Account Teams offer.
I don’t think it’s A. C is better if you want controlled case sharing and leaving Opportunities untouched is a common trap here.
Yeah A is the best fit. Account Teams let you set up read-only on Accounts and Cases but no Opportunity access, then add temporary access when needed. That matches private org-wide defaults with granular control. Pretty sure this is what Salesforce expects for this use case, unless I missed a detail.
It's A. The trap here is B, since Case Teams don't handle Account/Opportunity access well enough for these needs.
A
Account teams let you set specific access levels for members on an account, including read-only on accounts and cases, plus no opportunity access unless added. I think this covers all the requirements pretty neatly.
Account teams let you set specific access levels for members on an account, including read-only on accounts and cases, plus no opportunity access unless added. I think this covers all the requirements pretty neatly.
Be respectful. No spam.
