Download: Field-level Security in Microsoft Dynamics CRM: Options and Constraints

So since CRM became xRM one of the most often requested things I hear is field level security.  Great idea?  Oh yes.  Built in to CRM4?  Um, nope. 

CRM has built in security roles and they are darn robust.  Whoever made this feature certainly had their thinking caps on that day.  The amount of detail and variety for data access is more than I would have thought of, and I’d like to think I’m pretty smart.  The 2 things missing from security roles….access (or heck even a list) to the hidden permissions and field level security.

Problem number one is resolved for MOST users by copying an existing role and dumb-ing it down from there.  Problem number 2 is more complex.

First, I challenge you to think, is field level security REALLY what you want?  Sure it sounds flashy and cool, but would a custom entity (which already has a place in the built in security model) accomplish the goal?  So, you think about it, talk to some smart people, draw some scribbles on a white board and come back with yup, field level security is just what I need.  So then what?

Then what?  Then you learn a bunch more about CRM/xRM (NOT a bad thing).  Here’s a download to a new whitepaper about offering field level security in your CRM.  My word of caution, READ it ALL before you go off to make CRM.  There are many details you need to be aware of and the typical (I do this) skimming of the whitepaper might just get you in some trouble.  No biggie, just read it, you’ll be fine.

Download details: Security and Authentication in Microsoft Dynamics CRM: Field-level Security in Microsoft Dynamics CRM: Options and Constraints

Comments

[Anne Stanton]

Two other items that we await. Team level security and ownership and Business Unit ownership of certain entities. I know team level security is coming in 5.0, but BU security is still on the wish list.