A support specialist needs to read East renewal o1 while handling a related case. The user cannot open the opportunity. The existing support profile lacks Opportunity Read, and Opportunity defaults are Private.
Provide a narrow repair: add object Read through a reusable permission set, share East opportunities Read-only, and prove o1 is readable while o2 and editing remain unavailable. Keep the baseline private.
You own the complete access incident handoff described in the brief. The next person needs working configuration and enough evidence to explain its behavior. Start with the business requirement, then keep each completed part while you add the next one. Your own saved state carries between steps.
A later task can expose a mistake that an isolated form would hide. A queue may exist without usable membership, a report may have the right title but the wrong population, and a rule may work for the example while rejecting an allowed record. Test those boundaries as you go. The final step asks for the operational conclusion or completed deliverable, and the checker keeps earlier requirements in scope.