Suggested by BILU BABU – Completed
Currently there is no way to control the security for advance find entities and all users having any read level access can see the enties in advance find. From a solutioning point of view, read level access would be required to be provided for certain roles, but those roles should not be able to search the entity in the advance find.
Field level security is an option but difficult to maintain if there are lot of fields and roles.
It is a suggestion that this kind of security settings will enhance the current security architecture of dynamics CRM and from a security role perspective, we should be able to define which entities can be enabled for advance find for a particular security role.
Status Details
With modern advanced find, only tables in the app are available to users to explore.
And apps support role-based access.
-
It would be great to have a setting "allow advanced find" within a security role as part of the "miscellaneous permissions" section
-
This would resolve a great privacy problem
-
It would resolve a big privacy problem due to the dutch AVG legislation
-
It would be great to have a setting "allow advanced find" within a security role as part of the "miscellaneous permissions" section. Reason : In this way we can solve a problem with General Data Protection Regulation (GDPR)
-
What a great idea. This would solve some of our problems with different legal restrictions without loosing the full functionality of CRM. Thanks BILU BABU for posting this idea !!
-
good idea! Would solve lots of problems regarding de dutch AVG legilation.
-
Field level security is necessary
-
What a great idea. This would solve some of our problems with different legal restrictions without loosing the full functionality of CRM. Thanks BILU BABU for posting this idea !!
-
Field level security is necessary
-
I think this would also help with user adaption to. As an Admin trying to teach views and Advance find, it is very difficult learning curve for users when they have visible access to every Entity, versus the 3 or 4 main ones they need to use. And it's quite a big list to scroll through.
- 1
- 2
- ›