Forum Discussion
Any equivalent to SP2010's "Impersonation Step" in PowerApps/Flow?
MicrosoftChad_V_Kealey - Back to your original question there are two types of flows:
1. Flows that run in background in response to events, like an item being added to SharePoint list. In this case the flow always runs with the connections that are defined by the authors of the flow. So you can define a connection that has permissions to update the list. This connection is used irrespective of the event that triggers the flow.
2. Flows that run manually based on the user clicking a button in the UI. In this case the Flow can run either in the user's context, OR in the connections defined by the Author. The Authors of the flow define which path is used.
As a result, yes, it should be possible to do what you need today.
Deleted - You can use the Action called "Mail - Send email" - it's the Teal colored one.
Stephen SicilianoRe #2, I am triggering a Flow from PowerApps, but there doesn't seem to be an option to specify in Flow or in PowerApps to make the Flow run in a specific context. How can this be done?
- Stephen Siciliano
Hello, When I was referring to the Manually invoked flows I meant using the "Flow button". This trigger can be used and start flows from inside of the Flow mobile app or the portal. This functionality doesn't actually work with the PowerApps app at this time.
Stephen Siciliano, can you comment on how the new ability to add SharePoint lists/libraries as Flow "Owners" impacts the execution context of the Flow (if at all)?
Specifically, I understand (hopefully correctly) that adding a list/library as an Owner effectively uses that object as the permissioning mechanism. Users with Edit permission to the list/library can edit the Flow; users that have Contribute permission can add items to the list and the Flow is triggered, but it appears to still run in the context of the Flow Author (or last Editor?).
Ideally, it would be great if there were a way to specify the run context per connection or per action in all Flow types (e.g.: on item creation or modification) as you can in manually triggered Flows.
