Principal user (type=8) is missing prvReadXXX privilege in Dynamics CRM–You have verified user’s security role. What’s next? {CRM Tips from the vault}

Follow my blog for more interesting topics on Dynamics 365, Portals and Power Platform. For training and consulting, write to us at info@xrmforyou.com
CRM tips from the vault – A series which I have started on request of my blog readers who are quite new to CRM. My blog focus on niche topics which mostly require a prior in-depth understanding of Dynamics 365. However in this series I will mostly cover the topics which are quite simple, used in almost every project implementations and more importantly have withstood the test of time.
Here is my Tip 5 – Where you may miss to check if you get the error “Principal user (type=8) is missing prvReadXXX privilege”
You may be asking me – Why on earth Debajit are you writing this blog? Isn’t the error too obvious. The user must be missing the Read Privilege. Well if that’s the case, then you are lucky. But what if you have verified that the user’s security role is perfect and he/she have the appropriate privilege to the record.

Trust me this can sometimes throw you off. Any may consume some valuable time of yours. This can actually happen if the user’s Access Mode is not set correctly.
As was the case in mine. I opened the user and navigated to the “Client Access License (CAL) Information” section. And below is what I found
We don’t know how but the user’s Access Mode was set to Administrative. All I did was change the Access Mode set to Read-Write.

Save the user record. And now when the user tries again, voila! the error is gone.
Now that was a cakewalk. Wasn’t it?
Hope this helps!
Debajit Dutta
(Business Solutions MVP)