Users can freely access entity records in some views but not the others – instead they receive the following error:
You do not have permission to access these records. Contact your Microsoft Dynamics CRM administrator.
Check that the views that generate “access denied” error do not include fields from the parent entity users do not have read permissions for. For example, if users have read permissions for Jobs but not the linked (parent) Client then the presence of any of the Client’s fields in a view will generate the error above. Note: it’s OK to include the lookup field itself – in our case it will show client’s display name.