Configure Microsoft Dataverse1 / 5
A functional consultant needs to ensure that the Salary column in the Employee table is visible only to users in the HR department. Other users should not be able to read, create, or update this column. What security mechanism should be implemented?
CorrectNot quite
Alex
Column Security Profiles provide field-level (column-level) security in Dataverse, restricting read, create, and update access on individual columns. Per Microsoft docs, you configure a Column Security Profile, add secured columns to it, then assign users or teams. This is the correct mechanism for restricting the Salary column to HR users because it operates at the column level, not the table level.
Business rules can hide columns on forms but do not prevent API or programmatic access — data remains readable through other channels. A security role with restricted table-level privileges controls access to entire rows, not individual columns. Hierarchy security controls record visibility based on reporting relationships, not column-level restrictions. Only Column Security Profiles provide true field-level data protection across all access methods including forms, views, and API.
Sourcelearn.microsoft.com
Create a free account to keep asking Alex — no credit card required.
Question 1 of 5
Get started free