Yes while it is connected to changes made to permission schemes in V11, the issue is strange because this happens to users who are not restricted on the doctype via permissions. The users are given broad doctype permissions which removes the Restricted icon visible at the top right end of your screenshot, however the error shown in the screenshot above persists. The first slides in the gif below shows the user does not have Restricted on his purchase order doctype yet the permission error pops up.
What makes it even more weird is the fact that in spite of the permission error which shows up, some of the transactions end up being completed, which means something is not right somewhere as you can see from the image below.
In our case, on ly one user was affected. Others were not. The curious thing is that there were no differences in their roles, i.e. My user has same privileges over EPRNext than the affected user.
I had the problem with Employees. I managed to solve it, but (BRACE FOR IT) I do not remember how I did it.
Now this user is having the same issue with tasks assigned by other users. He can see tasks fine, but tasks with assignment from others he cannot see.
Probable solution: Make sure to be logged in as Administrator whenever you change any permissions.
Even if the Role Permissions are set per doctype, just check to make sure they are.
Go to the user. Remove the roles. Save. Add the roles back again. Save.
This should restore visibility and unrestrict the doctypes.
Now that I rechecked still have not resolved this, it was showing on “employee balance leaves” report as I did not have much time I left it as it is that only managers can view that report. For other employees it still shows this error