Today we look at the field-level security controls, as we know, the permissions control before the Dynamics CRM system is role-based, so the granularity is large, and in the new system, the field-level permission control is introduced, and the read operations, update operations, and creation actions are subdivided into the fields. Very to the force, of course, the configuration process is not complicated, let's take a look at it:
First we need to turn on the security options for the field
Then configure the access restrictions for that field in the security module, as well as the users and teams that can be accessed
Control of the CRU can be set
The actual effect, the user without permission is not able to do any action on the field
Users with Permissions
The above configuration just for everyone, this feature to the API is also in effect, if the user does not have permission to read the field on the UI, then through the API is not.
Dynamics CRM New Feature (7): Field level Security mechanism