Permissions for Secured Columns Access

Correct Answers: B, C and D

Dataverse provides column (field) security on a column by column basis for most out-of-the-box tables.

For management simplification, Dataverse groups the secured column (field) permissions into a profile.

A system administrator can grant access to the profiles to specific users or teams.

When system administrators create a column (field) security profile, they need to set the three permissions for each secured column (field):

All other options are incorrect.

For more information about Dataverse Field Security Profiles, please visit the below URLs:

When creating a Field Security Profile in Dataverse to restrict access to certain columns, you need to specify the permissions for each secured column in the profile. The three permissions that you need to set for each secured column are:

1. Allow Read: This permission allows users to view the data in the column. Without this permission, users won't be able to see the contents of the secured column.

2. Allow Update: This permission allows users to modify the data in the column. Without this permission, users won't be able to edit the contents of the secured column.

3. Allow Create: This permission allows users to add new records to the table that contain data in the secured column. Without this permission, users won't be able to create new records that contain data in the secured column.

The other answer choices provided (Allow Delete, Allow Save, and Allow Copy) are not relevant to setting permissions for secured columns in Dataverse.

In summary, when creating a Field Security Profile for secured column access in the Dataverse database, you need to set the permissions for each secured column in the profile to Allow Read, Allow Update, and Allow Create.