web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / CRM Cooking / Field Security changes in C...

Field Security changes in CRM 2015

Views (1172)
anilambadan Profile Picture anilambadan 1,160

Record-level permissions are granted at the entity level, but you may have certain fields associated with an entity that contain data that is more sensitive than the other fields. For these situations, you use field level security to control access to specific fields.

The scope of the field level security is organization wide and applies to all data access requests including the following:

  • Data access requests from within a client application, such as web browser, mobile client, or Microsoft Dynamics CRM for Outlook.
  • Web service calls using CRM SDK (for use in plug-ins, custom workflow activities and custom code)
  • Reporting (using Filtered Views)

One of the big limitations of Field Security in previous versions of Dynamics CRM was that it was only available on custom fields and not on out of the box fields. In Dynamics CRM 2015 its changed,  Field Security can now be enabled on most out of the box fields, with only certain system fields such as the primary key/primary field or status/status reason not having Field Security as an option.

field

Best practices when you use field security

When you use calculated fields that include a field that is secured, data may be displayed in the calculated field to users that don’t have permission to the secured field. In this situation, both the original field and the calculated field should be secured.

Some data, such as addresses, are actually made up of multiple fields. Therefore, to completely secure data that includes multiple fields, such as addresses, you must secure and configure the appropriate field security profiles on multiple fields for the entity. For example, to completely secure addresses for an entity, secure all relevant address fields, such as address_line1, address_line2, address_line3, address1_city, address1_composite, and so on.

When a system administrator implements security for particular fields or records, it can affect the data that’s synchronized between Microsoft Dynamics CRM and Outlook, including the inability to push data to the user running CRM for Outlook. Before you secure a field, consider how it may affect your users that are running CRM for Outlook. More information: How field security affects synchronization between CRM and CRM for Outlook

Video: Field Level Security in Microsoft Dynamics CRM 2015

For more details visit:

https://technet.microsoft.com/en-us/library/dn832104.aspx

thanks for reading my blog :)



This was originally posted here.

Comments

*This post is locked for comments