cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Frequent Visitor

Prevent user to save/change data directly in Sharepoint list, the data will save/change though Powerapps only

Dear All,

 

I have build Powerapps application connected with SharePoint and I want to prevent user from save/change directly in SharePoint list, the data will be save/change through Powerapps only, Is there any solution to do that?

 

Thanks in advance.

1 ACCEPTED SOLUTION

Accepted Solutions
Dual Super User III
Dual Super User III

Just to add.  For #1 you'll have to de-link it and go through two Flows in order to save results using Flow without permissions.  Any Flow that you call directly from a PowerApp will run in the security context of the user.  So you will have to call another Flow from that Flow to get the Flow to run in the context of the person creating the Flow rather than the one executing the PowerApp.  PowerApps just isn't designed to be a security application in front of SharePoint.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

4 REPLIES 4
Dual Super User III
Dual Super User III

There is no way to keep users from editing a SharePoint list directly but still allowing them access to the list through PowerApps.  Users must have permission to access the list to use it in PowerApps and that gives them permission to edit the list directly.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Continued Contributor
Continued Contributor

As @Pstork1 mentions, you cannot do this *unless* you either:

  1. De-link your PowerApp from SharePoint and instead link it to Flow (or some other in-between)
  2. Stop your application from performing a SubmitForm() on certain users (which I think would work)

Depending upon your environment and how much business logic you have piled into your app, I might suggest one vs. the other.

Dual Super User III
Dual Super User III

Just to add.  For #1 you'll have to de-link it and go through two Flows in order to save results using Flow without permissions.  Any Flow that you call directly from a PowerApp will run in the security context of the user.  So you will have to call another Flow from that Flow to get the Flow to run in the context of the person creating the Flow rather than the one executing the PowerApp.  PowerApps just isn't designed to be a security application in front of SharePoint.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

Continued Contributor
Continued Contributor


@Pstork1 wrote:

PowerApps just isn't designed to be a security application in front of SharePoint.


Exactly.  You're really supposed to be doing the security layer within SharePoint itself.

Helpful resources

Announcements
secondImage

Experience what’s next for Power Apps

Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

New Power Super Users

Congratulations!

We are excited to announce the Power Apps Super Users!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

Top Kudoed Authors
Users online (66,617)