Field-Level Security in Microsoft Dynamics CRM: Options and Constraints


The CRM E2 team is pleased to announce the release of the white paper Field-level Security in Microsoft Dynamics CRM: Options and Constraints, a component of the broader CRM E2 Nuts and Bolts article on Security and Authentication in Microsoft Dynamics CRM, which is available for download from the Microsoft Download Center at:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=471f8670-47b3-4525-b25d-c11a6774615c


This document provides selected aspects of the conceptual application of the Dynamics CRM security model, with details about the various options and constraints that are associated with using supported custom logic to control of access to data at a more granular level than is provided by Microsoft Dynamics CRM out-of-the-box.


The CRM E2 team especially recognizes the efforts of Roger Gilchrist, Mahesh Hariharan, and CRM Product Development for contributing to and reviewing this paper to help ensure its completeness and accuracy.


Thanks,
Jim Toland






Comments (5)

  1. Peter Hale says:

    Be great if the download of the pdf existed

  2. Sami says:

    Good document.

    I have been trying this approach of writing plugins at various levels to prevent unathorized data from being displayed. However i have noticed that if a user wants to hide an attribute like say the Currency attribute, if we remove this attribute from the Post retrieve result, the CRM form will crash if any of its money attribute had non-zero value?

    What can be done to prevent this apart from not allowing users to hide this attribute as a part of security restriction? Currency is just one example but i have seen this happen with other types/attributes as well.

    Any suggestions?

  3. MBowen says:

    The download link is still broken.  Any idea of when that might be fixed?

  4. crmblog says:

    Funny the link works for me and my neighbor. Can you get to the Microsoft Download center and then search for it there? If not, I’m guessing it’s a connectivity problem.