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.
Microsoft Dynamics
Last Comment
Feridun Kadir
8/22/2022 - Mon
Feridun Kadir
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?
josefmikhail1984
ASKER
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.
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?