Supervisors (Security roles): In Dataverse, Security roles are the primary mechanism for defining a user's access level to specific table types (entities). They define permissions such as Create, Read, Write, and Delete based on ownership or business unit hierarchy.

Salespeople (Field level security): When specific sensitive data within a record (like a social security number or credit limit) must be restricted while the rest of the record remains visible, Field-level security (Column-level security) is the appropriate tool.

Developers (Environment security): To manage who can create resources, apps, or flows within a specific sandbox or production instance, Environment security (assigning roles like Environment Admin or Environment Maker) is used to control access at the container level.

Microsoft Learn (Power Platform Security): "Security roles and privileges" section. Describes how roles define access to data and UI components. (Document ID: wp-security-dataverse)

Microsoft Learn (Power Platform Admin): "Control user access to environments: security groups and licenses." Explains how to restrict developer and user access to specific environments.

Microsoft Learn (Dataverse): "Column-level security to control access." Details how to restrict access to specific columns (fields) within a table.

Microsoft Power Platform Guidance: "Security Architecture" (Whitepaper). Section 3.2: Defining Organizational Security Boundaries.