A company plans to use Microsoft Dataverse to manage sales opportunities.

Sales representatives — User-level access; Sales managers — Organization-level access

User-level access is the correct depth for sales representatives because it limits table privileges to records they own or create. The security role can grant Create, Read, Write, and any required related privileges at the User scope, ensuring that one representative cannot automatically open another representative’s opportunity. Sales managers require Organization-level access because the requirement explicitly states that they must see all opportunities in the organization. Organization depth applies the permitted operation across business units, unlike Business Unit or Parent: Child Business Unit depth, which would restrict visibility to part of the hierarchy. The actual role should grant only the operations managers need; organization-wide Read does not necessarily require organization-wide Delete. Field-level security should be added separately if particular financial columns require tighter control than the row itself. Sharing and team ownership can address approved exceptions without broadening the base role. The Study Guide’s exact data-model objective is “configure security.” This mapping implements least privilege at two different record-access depths while preserving the required managerial visibility.

Study Guide reference/topic: “Build data models — Configure security.” AB-410 Study Guide | Microsoft Learn technical reference