This Security Role would hold only those privileges that allow a user to login into Dynamics CRM or to phrase it in another way, without these privileges, you would receive the error “You do not have permission to access these records. Let’s create a new Security Role by the name “Log-In”. This blog post will drive you through it! Sounds Good!īut, what could be the bare minimum privileges for a user to at least log-in into the Dynamics CRM?
With this case, it might be better to start from the scratch and add the privileges rather than pick one of the existing and start modifying it.Ĭreate a Security Role, with bare minimum privileges. Most of the businesses have their own set of Roles, which do tend to differ from the predefined Security Role Profiles.įor a start, the predefined Security Role Profiles could come handy where your task would be to just turn on or off the privileges for a few of the entities, from say Salesperson profile and there you have the Security Profile that you are trying to create.īut, there could be a scenario where you are trying to create a Security Role Profile, that is completely different from any of the predefined Security Role Profiles. However, not all businesses revolve around these profiles or roles. One needs to be very careful while selecting privileges for the Security Role creator.ĭynamics CRM ships with few of the most commonly used Security Role Profiles like Salesperson, Sales Manager, etc.
Earlier we had the issue with insufficient permissions and then a few days later we had a request to fix a new security role created by a power user.ĭefining a Security Role has always been a daunting task. We have been working a lot with security roles recently.