cancel
Showing results for 
Search instead for 
Did you mean: 

Flow, sent the emails by the flow launcher (not its creator)

Hello,


Having dealt with a Microsoft Business Intelligence Engineer of Microsoft Flow, he informed me that my request did not yet exist in the design of microsoft flow.

 


My request :


Currently:
The flow is created by its creator (The flow will be launched each time by a different user (dynamic)).
The creator shares the flow with his team (so that any user of the team can launch it).


A "person X" starts the flow. "Person Y" receives the request for approval (By "Start an Approval).
But this request for approval is sent by email with the email of the creator and not the "person X".


Likewise for an update of a sharepoint column:
The flow is started by the "person X", the flow modifies a sharepoint column of the file, and the column "modified by" displays the creator of the flow, and not the "person X".


So to summarize, currently:
If the Flow should be sent by "Person X" he should create a Flow with the same things what Creator has created...

 

So the idea that our company would like:
Be able to send a flow (created by its creator) by a "person X" by taking the connection information dynamically.

 

 

Thank you very much in advance for taking charge of our request.

Status: Completed

Hello -- when you manage the run only access for your flow you can configure whether or not the connection should come from the flow owner - or - the person who is launching the flow. You can read more about this feature here: https://flow.microsoft.com/blog/advanced-button-sharing/

Comments
Level: Powered On

Yes!  Please make the name of the person sending the approval emails or modifying the data the person that starts the flow - not the person that created the flow.

Level: Power Up

This seems an obvious requirement to me.  Please .

Level: Powered On

Agreed. Yes please have this rectified asap.

Thanks,

Charlu

Level: Powered On

How was this overlooked?

Level: Powered On

Please!  Makes no since for Team flows!