How to redirect users to the Power Apps app from SharePoint

This video walks you through how you can secure the SharePoint Online list which is a data connector for a Power Apps App. The video demonstrates how using a control column on SharePoint list and Power Automate flow can secure the content.

You have the option to disable the quick edit mode in the list settings. Also change the permissions from Edit to Contribute, this allows the user only add/edit the content and not any settings.

Interested in my blogging gear? Then take a look at them on Amazon:

[kcraigo]

This is great Daniel. I can see an additional feature request in regards to the notification if the user uses the Quick Edit, maybe have the Flow send a link to the Power App but their data is pre-filled in the Power App, to keep them from having to retype. Fantastic demo.

[santukondapally]

I really love your explanation towards technology. you are true inspiration to learners like me. Just want to give compliments .

[brightonalbert]

Thanks alot christian, i was having trouble with user who know how to use sharepoint. will definitely use this and will preventing double entry will figure that out too

[ebukagnwa]

Hi Daniel, Thanks for sharing such ideas through your video. It's of immense value to me & i hope others too.

I have a question: What way did you set up the customised list that shows up when "New" Button is clicked. Thanks in anticipation.

[kcraigo]

Sorry I forgot, in the List settings - Advanced Settings, you can disable Quick Edit.

[Billbear]

Thank you Daniel, do you do this by default for security conscious clients? i feel I should do this method as default..

[deviprasad.r.shetty]

Hi Daniel good video. In demo you have changed form on click of new form in SharePoint list is this achieved by PowerApps modifications or any other approach.

[rorysketch]

Great job. A couple of thoughts:- I guess the new item would be in the name of the flow owner? Also, building on what you've done couldn't you just make the Control field mandatory, that way they couldn't quick edit their way into it (not sure if all fields show, but I think they don't). Like the way you force them into using the app with the form. Makes Dev/Test/Prod interesting.

[jakeli]

I love this idea and all the videos you've posted.

However, this may not be the best approach in dealing with the control over unexpected update of the SharePoint list behind the apps. This will even make the requirement of allowing users to edit the items they have created more complicated than it needs to be.

If you really want to prevent users from updating the list items in the SharePoint and only allow them to do it via the apps you've provided, you'd better configure your SharePoint list by 1) giving users merely the Contribute role to the list rather than the Edit (with Edit role, users will be able to change the design of your list); 2) enabling the Allow Management of Content within the Advanced Settings of the list; 3) changing the Status to Hidden for items that you don't want users to change via the default SharePoint list form in the Content Type settings; 4) disabling the Quick property editing feature in Advanced Settings.

[cvkealey]

There's one other end-run scenario that folks need to know about: classic mode. As long as that still exists (or until MS gives us a way to block it via a site setting or feature), users will be able to "switch to classic mode" and create new items. The classic "new item" form will (by default) show all of the fields/columns from the list, but you can enable Content Types on the list and set certain fields (like the "control" column) to be hidden.

[SiMataR]

Great video! Thank you for this.
The next level is how to get rid of the read permission for users to the secured list by letting only the app maker pass user data thru flow to the power apps user gallery.
I cannot figure out how can automate pass items from sharepoint to powerapps as an array or string that will be parsed in powerapps.

[juansepowerplatform]

Great, I was looking for this idea. I guess the only way Gabriel can tinker with the data is by adding Control = "True" on the first list where he has edit rights. Or how do you control that field from not being filled out manually (Control field). Thank you for sharing knowledge

[bharatshinde]

Hi Daniel,
Thank you for this video. I like your idea of moving data to #2 secure list and giving users READ rights. But in normal app scenarios, user wants to update their records. Since we are giving READ rights, updating will not be possible. Any thoughts?
Bharat.

[AcePlays]

Hi Daniel, I love your work! I think still we have a problem here.
As Keith mentioned you can disable quick edit and custom views. But everyone has App maker rights. So if some one create an App and add the first SharePoint list now that App can view/Add/edit all the fields including the "control" filed :(
I feel like there is no way to 100% secure the database (SharePoint) without paying for a premium connector (CDS or SQL).

[jeffwilliams]

It seems to me that since you can disable the quick edit functionality then you don’t need to actually copy to a second list since you have effectively taken away both the users options to add data to the list outside the app (Sharepoint classic mode excluded).

Or am I still missing something.