Forum Discussion
Any equivalent to SP2010's "Impersonation Step" in PowerApps/Flow?
MicrosoftHello, 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.
- Stephen Siciliano
Your understanding is correct.
Unfortunately, for the second part (run in arbitrary context per action), this isn't something we support today but we'll consider it for the future.
Stephen Siciliano, so the only way to have control over whose credentials are used for the connections would be to use manually-triggered Flows? Are Flows initiated from a PowerApp (e.g.: via a "Submit for Approval" button) considered "manually-triggered"?
- Stephen Siciliano
That's correct. At this time PowerApps triggered flows don't use the same capabilities as button flows (aka manually triggered).
