Prevent people from accessing SharePoint list that the PowerApp is connected to

[AnnaBrodnicki]

I'm building a marketing studio time request app that doesn't contain personal information but business sensitive information from the point of view that we don't want people to see other people's submissions due to the inernal politics that might result from it.

I am setting up the powerapp so that staff can submit their time requests and then can go back into the app and view/edit their own submissions only using a formula based on user.  The data source is a SharePoint list.  I understand that in order to add/edit from the PowerApp they need to have the relevant permissions for list in SharePoint.  

So the PowerApp will act as the front end for the submissions and the SharePoint list will act as the back end for the team processing the submissions.

I don't want people in the organisation to be able to access the SharePoint list and view other people's submissions/list items or have the ability to edit other people's submissions/list items.

I could hide the SharePoint list as much as I can by not having it on navigations etc and even create a default view that contains bare minimum info in case someone does navigate there but I feel it's still open to being discovered and information viewed.  This is a worry for any future apps that I might create that contain personal data or business sensitive information.

Does anyone have any suggestions about the best way to control this and prevent people from accessing the Sharepoint list that the PowerApp is connected to? 

Thanks,

Anna

[EP3]

Hi, Thanks for the response, but I believe I have worked it out and it's really simple:

I build an app in a production environment using dataverse tables within that environment, I share the app to people who don't have access to the environment, they can access the app, and any data it pulls from the tables, but can never open the dataverse tables or use them in their own apps because they can't access the environment.  Is this how it works?

[kky1]

THANK YOU @Adam_116

Almost 4 years later and your response is still helping people!

@kky1