Announcements
We are making some changes to our processes, and one of the entities we currently use, we do not want to use going forward, but want to maintain the data. We are thinking of adding security to the entity so that only a few can view it, and so that it cannot be used with various Power Apps in our environment. Would creating a security group be the best way to solve this issue?
Hello @smw356239,
The best approach in my opinion would be to use security roles. Only users with a security role that explicitly allows access to the entities can access the data in any way, e.g. using an app, flow, or through the API.
You can find more information on security roles here.
And you can assign a security role to a security group you created as a team in Dataverse, so you can combine this with your idea about security groups.
tks u
Hi @smw356239 ,
Yes. It's a good practise to restrict use of this entity by creating a security role and assigning permission to users who possess that role only. Also you need to take care of removing the access to this entity from all existing security roles as well. System Admin and System customizers will continue to have access to this entity.
-------------------------------------------------------------------------If I have answered your question, please mark your post as Solved.If you like my response, please give it a Thumbs Up.
My Blog: Dynamics 365 Key Topics – https://d365topicsbydk.com/
My YouTube Channel : https://www.youtube.com/channel/UCxSIryP2ah2VpEFr-Z72t1A
RegardsDevi
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our community stars!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 393 Super User 2026 Season 2
Mohsin Ali 328
WarrenBelz 278 Most Valuable Professional
