?
Solved

Security permission settings in CRM Dynamics 2011

Posted on 2013-12-06
3
Medium Priority
?
459 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

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

Having trouble getting your hands on Dynamics 365 Field Service or Project Service trial? Worry No More!!!
Desired Skill Set for Microsoft Dynamics CRM Technical Resources – Part II
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
Suggested Courses
Course of the Month11 days, 22 hours left to enroll

752 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