Solved

Security permission settings in CRM Dynamics 2011

Posted on 2013-12-06
3
431 Views
Last Modified: 2013-12-13
Judging from the permissions in CRM it doesn't seem to allow you to distinguish what a user can see when it comes to a particular account.

You can set the security on a number of fields for all accounts they have access to but we are trying to get it to work so they can only see a number of fields or entities on a particular account and so forth.

Is this even possible with CRM outside the base package scope?

Thanks.
0
Comment
Question by:josefmikhail1984
  • 2
3 Comments
 
LVL 29

Expert Comment

by:feridun
ID: 39701490
The records that a user can work with depend on the settings in the security roles that the user is assigned.

The security role determines the privileges that a user has (e.g. create, read, update...) and the extent to which the user can exercise the privilege (own records, records owned by anyone in the same business unit as the user, etc).

You can apply field level security to custom fields but not out of the box (system) fields.

Can you post a more general high level description of how you would like security to work?  Do you want everyone to see all accounts but some people only some or some other variation?
0
 

Author Comment

by:josefmikhail1984
ID: 39701499
Thanks for your answer.

Your last paragraph summed up what I was after.

Lets say User A can see every account there is in the system.

User B can see some of the accounts that User A can see.

User A can see everything in those accounts as the owner but the Administrator would like to restrict what areas he/she can see on specific accounts.

Same goes for User B.

Hope this is clearer.

Thanks.
0
 
LVL 29

Accepted Solution

by:
feridun earned 500 total points
ID: 39701525
I think I see and I think the answer is no.

If the fields that are to be restricted are custom fields then field security can be used to restrict whether someone can work with those fields but the field security applies to the set of accounts that the user has access to via their security roles.

There is no out of the box method for restricting one or more fields on one or more accounts from a user.

If the fields in the accounts that need to be restricted comprise sensitive information an option might be to move them to a custom entity and then secure the custom entity differently from accounts.
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

This is a walkthrough guide I wrote whilst upgrading my on-premise MS Dynamics CRM 3.0 deployment to 4.0. This covers the actual installation of the product to a working level for my system, I ran into a lot of issues that the steps below fixed so h…
On Sep 22nd 2014 Microsoft released Update Rollup 1 for Microsoft Dynamics CRM 2013 Service Pack 1 and back in July Update Rollup 3 was released.  So we now have:   Update Rollup 1Update Rollup 2Update Rollup 3Service Pack 1Update Rollup 1 for S…
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now