Key benefits

EM for Microsoft Dynamics CRM provides the following features.
  • Enforcement based on the Dynamics CRM entities:
    • Secure by default: When security enforcement for a Dynamics CRM entity is turned on, users do not have access to any records, until explicitly granted by policy. Access includes view, edit, and delete.
    • Full record level data filtering: EM for Microsoft Dynamics CRM uses entity and/or user attributes to control read access. Users cannot access their own records by default unless the policy grants them access.
    • Field Level data filtering: EM for Microsoft Dynamics CRM uses “Mask Field” obligation to control field read access.
  • Enforcement based on the user attributes: EM for Microsoft Dynamics CRM gets the user attributes from the native CRM user records. These attributes are used for authorization decisions.
  • Supported actions: View, edit, or delete entity.
  • Supported obligations:
    • Apply Security Filter: Allows EM for Microsoft Dynamics CRM to filter entity records based on the user attributes and the entity attributes. The obligation supports User-Attribute types and Entity-Attribute types listed below.
    • Display Policy Violation Message: Displays a message to users when a policy violation happens.
    • Inherit Policies From: Allows EM for Microsoft Dynamics CRM to filter entity records subjected to the policy against its “secured” direct parent entities.
    • Apply Security Filter Based on Parent Attributes: Allows EM for Microsoft Dynamics CRM to filter entity records subjected to the attributes against its “secured” direct parent entities.
    • Mask Fields: Allows EM for Microsoft Dynamics CRM to mask specific fields in a record with specific masks.
  • Supported user-attribute types:
    • Picklist
    • String
    • Integer
    • Lookup. This is supported only in value fields in the resource component conditions.
    • Boolean
    • Date. This is supported only in obligations.
    • Null
  • Supported entity-attribute types:
    • Picklist
    • String
    • Decimal
    • Integer
    • Boolean
    • Currency. This is supported only in currency values without currency unit. On edit action, ensure that you specify whole numbers followed by four decimal places. For example: 123.0000.
    • Date. This is supported only in obligations.
    • Null