Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Security permission settings in CRM Dynamics 2011

Posted on 2013-12-06
3
Medium Priority
?
464 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 30

Expert Comment

by:Feridun Kadir
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 30

Accepted Solution

by:
Feridun Kadir earned 1500 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

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For cloud, the “train has left the station” and in the Microsoft ERP & CRM world, that means the next generation of enterprise software from Microsoft is here: Dynamics 365 is Microsoft’s new integrated business solution that unifies CRM and ERP fun…
Desired Skill Set for Microsoft Dynamics CRM Technical Resources – Part I
Integration Management Part 2
This lesson discusses how to use a Mainform + Subforms in Microsoft Access to find and enter data for payments on orders. The sample data comes from a custom shop that builds and sells movable storage structures that are delivered to your property. …
Suggested Courses

824 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