Hide Dataverse tab in Power Platform/Avoid users from making edits directly in Dataverse DB

[kkarikar]

Hello everyone,

I researched for days and haven't found any documentation on this. I apologize if this is not the right forum to post this. If it isn't, please direct me to the right place.

With the new Dataverse update our team is concerned with having an easy access to edit data in all data tables in dataverse. 

Users can access apps shared with them via App tab and within the app we have security which changes during different stages of our application process.

Example: If a user has security role where they're able to create a record, write/edit a record in a table "Test". During an approval process that the record goes through, this user is not allowed to make changes to that record in "Test" table in the canvas app (we have used logic to disable some edit/save buttons). But, this user can go into the dataverse tab (highlighted in Screenshot 1), look for "Test" table, and edit that record (Screenshot 2) which we want to prevent. 

"Dataverse" tab can be easily opened by users, they can access the tables and edit data accidentally/intentionally. We want to avoid users from making changes directly into the Dataverse DB as this can alter the process flow in the application.

If hiding the Dataverse tab itself it not possible, I am very open to workarounds. I am not sure if it is possible to hide tables in dataverse from users. Or if there is any security role set up to accomplish this.

Thank you so much in advance!

[rampprakash]

Hi @kkarikar 

Am afraid it is not Possible.

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Follow me on Twitter : @rampprakashd
Blog : https://microsoftcrmtechie.blogspot.com

[Mira_Ghaly]

@kkarikar 

What are th security roles assigned to these users?

I believe if they don't have environment maker or system customiser roles then they won't be able to access the maker portal.

[kkarikar]

Hi @Mira_Ghaly,

We have created a custom role with minimum privileges required to run a canvas app (every user has this role) and additional custom role for users with create/write privileges on custom tables (this is different person by person due to their roles in the system).

These are the custom tables we don't want them to edit from DB directly during a specific process stage in our canvas app. Other times, these users are allowed to make edits/create new records in custom tables they have access to but always only through canvas app and never directly from dataverse. 

Please let me know if you'd like more information.

Thank you so much for your response.

[AhmedSalih · Accepted solution]

@kkarikar, I had a similar requirement and my users had Read/Write Access on Custom Tables. On that Custom Security Role, I made sure they don't have any Customization access: 

**Again, they don't have Create Access so I am not sure if that would make a difference.

Now, If they try to access the Dataverse, this what they see:

Regards,
Ahmed
If my reply helped you, please give a 👍. And if it has solved your issue, please consider Accept it as the Solution to help other members in the community find it more.

[Mira_Ghaly]

@AhmedSalih 

This looks correct to me but not sure what can be done in @kkarikar case where he need the create permission, so disabling customisation is definately correct but not sure what is the case if the create permissions are there, I will replicate in my environment and will let you know.

[kkarikar]

Thank you @AhmedSalih! I implemented the solution and it worked for me!! 🙂

[kkarikar]

@Mira_Ghaly , thank you for your help! 🙂