Make Strategic Use of Microsoft Dynamics CRM Security Settings

Configuring data security within Microsoft Dynamics CRM is a complex aspect of an implementation that many companies just don't take into consideration during the planning stages.  But the benefits can extend beyond basic data breaches into areas like user adoption and business process design.

"One of the challenges is that there are so many pieces to the security picture that it's important to know what's out there so you can drill in and make the choices on how to configure your security appropriately and make only the changes you want to make," said Scott Sewell, CustomerEffective Dynamics CRM Technical Specialist and a Microsoft MVP, at a recent online meeting of the Dynamics CRM User Group.

Companies have to take the time to plan to have successful security models and successful implementations that gives users access to the records that the need but hides or protects information that they shouldn't see based on their roles within the business, Sewell said.

"Number one, resist complexity," he said. "The more complex and nuanced your security model the more difficult it is to manage, test and verify."

Sewell said companies should use security to hide objects that a user doesn't interact with at all.

"For instance, if you have an implementation that's oriented to the service module and the sales team has not come over and started using CRM, then there's no point in showing visibility into orders and invoices and quotes in CRM," he said. "Use security to hide that and make CRM easier to navigate by showing only the objects that are actually implemented in your organization."

Companies should also "pre-document" their intent, which will help for ...