(Original title: Multiple users should be able to run a flow (not only owners)) Currently only the owners of a flow are able to run it, this is a huge this advantage, this means only the people that is creating and modifying the flow are the only people that is able to use it. I'm aware about the sharing option for the button triggered flows, however, I'm talking about all the other triggers, the ones that work based certain thing changing or something new being added to the platform, the kind of things are actually worthy to automate. Image a simple scenario, there is a SharePoint Library where an approval process must run when any internal user with access to the library creates a new document, surprinsily, even that users have the proper license for MS Flows, the flow is not triggered, only the flows owners are able to run it. For sure the previous example can handled by using the classic workflows, however, this is about of evolving, taking advantage of new technologies and opening the door for new possibilities. I don't understand why this extremely elementary functionality was not included in the first place.
... View more
As covered in the comment, we currently have this functionality for button triggered flows, as well as for a selected item. However, for flows that run in the background they must run in the context of someones account. It doesn't actually have to be the owner's account, but the account can not be dynamically selected at runtime (e.g., if Fred uploads a file, the flow cannot run in the context of Fred since he has not granted consent to Flow to use his authorization context). That being said, this is something that we are now planning on improving in the future.