Field-Level Security in Microsoft Dynamics CRM
Recently I came across the blog article Field-Level Security in Microsoft Dynamics CRM : Options and Constraints (at http://blogs.msdn.com/crm/archive/2009/11/16/field-level-security-in-microsoft-dynamics-crm-options-and-constraints.aspx ) which talks about restricting attribute level access to certain users based on the different access channels for users to Microsoft Dynamics CRM. On the client side, one of these ways can be used – a. Passing an indicator to the field to display to the user that they user cannot view the attribute e.g. ‘******’, ‘Restricted’, ‘Not Authorized’. b. Making fields read only or hidden if a user is not authorized to view them. Server Side Restriction –Two strategies are basically proposed: 1. Role based filtering - If the user does not have a role that is entitled to access the attribute then it will be restricted. An advantage of role based filtering (and a reason for its simplicity) is that the access to an entity’s attributes can be defined without need...