Why CRM Security Is Always a 'Role'-Your-Own Project

With most enterprise applications, the security model can be simply user/group/world. It can't be all that complicated with CRM, right? Think again.

By David Taber
Wed, April 03, 2013

CIOCRM systems are the most political of all enterprise software applications. This is partly because of the user community; sales and marketing play politics for a living. It's also due to the data in the system, as a single CRM table—the forecast—can make or break careers. Exactly who sees what, and when, is a key issue in organizations of any real size.

Tips: How to Get Smarter About CRM Security

Every CRM system has a slightly different security model, but there are general principles that apply everywhere. This article focuses on the Salesforce.com access control and privilege model. It's complicated enough to be frequently misunderstood—which makes it a good example for illustrating key issues.

Core Privileges: Start With Exclusions, Then Add Exceptions

Salesforce security has several overlapping layers that focus first on exclusion, then on adding access as exceptions to the exclusion. In small systems, most of the filtering is turned off. This can lead to some nasty consequences, so larger organizations must use every filtering mechanism available to keep data quality up and compliance issues down.

The first exclusion filter is specified by the class of user, or profile, and is applied at the object (table) level: Is a given profile allowed to see an object at all, and, if so, what operations are generally allowed? In addition to create, read, update and delete, there are privileges to "change record owner," "be allowed to see any record of this object, even if you shouldn't otherwise be able to" and "execute certain classes."

The next level of filtering is at the column level. This enforces three levels of access: Hidden, read-only and read-write. Profiles also define system-wide privileges (for example, export report data), but most aren't object-specific and therefore not a big deal.

Tips: Too Much Access? Privileged Identity Management Can Help

If you've created a bunch of customer fields and installed lots of applications in your CRM, this may mean you can set 1,000 attributes or more for each profile. Don't worry, it'll get more complicated soon enough.

Continue Reading

Our Commenting Policies