In keeping with our extensive support for Microsoft applications, NextLabs now announces the release of its latest version of Entitlement Manager for Microsoft Dynamics 365 (EM for Dynamics), Microsoft’s CRM application.
We listened to our customers, looked at where the market was headed, and added features consistent with the NextLabs mission of protecting data whether at rest or on the move. This latest release also reflects our deep commitment to the Microsoft stack, augmenting our current support for SharePoint, Exchange, and Outlook.
EM for Dynamics reinforces that commitment with even more granularity and flexibility for Dynamics CRM.
“Refresh my memory . . . what is Microsoft Dynamics again?”
Microsoft Dynamics CRM is a multi-faceted platform where everything you need to develop, enhance, and retain your client relationships is stored. It centralizes customer information, business intelligence, the ability to track sales opportunities, and more in one application. EM for Dynamics sits on the Microsoft Dynamics CRM Server and works with both on-premises and cloud deployments of Dynamics.
“What are the potential landmines of Dynamics?”
The ease with which Dynamics CRM enables collaborators to share data and manage their own fine-tuned access controls can lead to serious risk exposure in terms of inappropriate data access, distribution, and loss.
To address this challenge, EM for Dynamics was developed to enhance compliance and security for this leading CRM application. It enforces policies on the application across different Dynamics entities, such as contact, account, and so on. Based on policies, EM for Dynamics filters entity records by user attributes and entity attributes. For example, the application can enforce policies to allow account executives to view only those accounts that match their business unit and industry.
“You’ll get nothing and like it . . .”
If your company has very strict controls over who can access what in Dynamics, NextLabs now enables you to shut off access to any records in Dynamics by default. With this policy turned on, users can’t access any records unless explicitly allowed by policy. Thus, users won’t be able to View, Create, Edit, or Delete without permission.
With this approach, enterprises ensure that that their users can only access the Dynamics 365 data they need to do their jobs and are not inadvertently given access to sensitive, classified, or regulated data.
“You can go to prom, but you gotta be back by 1am”
If you don’t want to opt for the “you’ll get nothing and like it” approach to data security and prefer some flexibility, EM for Dynamics now allows you to filter data either at the record level or the field level. You can even make authorization decisions based on user attributes from the native CRM user records.
These new features ensure enterprises have the flexibility to control access to data as granularly as needed by the business or as required by policy – either at the object or field level. They also give enterprises an easy way to make actionable information available to users who would otherwise be denied access to data by policy.
Here are some other examples of the flexibility now afforded by EM for Dynamics:
- Apply Security Filter: Allows the filtering of entity records based on the user attributes and the entity attributes
- Display Policy Violation Message: Displays a message to users when a policy violation happens.
- Inherit Policies From: Allows the filtering of entity records subject to the policy against its “secured” direct parent entities.
- Apply Security Filter Based on Parent Attributes: Allows the filtering of entity records subject to the attributes against its “secured” direct parent entities.
- Mask Fields: Allows the masking of specific fields in a record.
For more info . . .
If you’re interested in learning more about NextLabs’ solutions for the entire Microsoft stack, and not just Dynamics, click here.