cancel
Showing results for 
Search instead for 
Did you mean: 

Add the From field on the action “Send Approval email”

Add the From field on the action “Send Approval email” like the "Send email" Action

Status: Completed

You can now customize who the Approval appears from - read more here: https://flow.microsoft.com/blog/button-types-more/

Comments
Level: Power Up

The Created by field in the email should be omitted. It is normally used in organizations and the do not want the name of the creator of the flow. Also, the translation of the Requested by field to Spanish is wrong. It is translated "Solicitado para" and it should be "Solicitado por". Also it would be a good idea if there is the posibility to write in the Requested by field a group email (Now it is only available for single user emails).



 

Level: Powered On

@oussamazebar Since the "Created by" field still shows the owner of the Flow, even when the Requester is set as the item creator, this problem has not been resolved.

Level: Powered On

I agree with @HC2019.  We need to ability to change the emails to not come from Microsoft Flow <maccount@microsoft.com>.  We tried to add a new connection in the approvals and simply receive: Failed to create connection for connection id '/providers/Microsoft.PowerApps/apis/shared_approvals/connections/shared-approvals-687BDD4F-CAAA-4C19-BB71-65E8DEBF4F36'. You have reached the maximum number of connections for the 'approvals' API.  

 

My company sees these emails as junk mail coming from Microsoft.

Level: Powered On

When using the template "Start approval when a new item is added" the requester field is not available.
Please add the field to this template (and any already created flows based on this template)

 

Also, please make it possible to change the from mail, as the maccount is also seen as spam in our organization. 

MJA
Level: Powered On

@Stephen 

I am not sure how this solution / fix applies to a non-approval workflow.  For example: 

  1. User X creates and publishes the Flow
  2. User A adds / creates a new SharePoint item to the list
  3. An email is sent to User A Manager to review the item; the email is sent from the Flow author (User  X).

The issue occurs in step #3.  I'm not sure how the approval updates in the blog applies to the above example for a non-approval flow -- where we just need to send an email, from the person who created the item in SharePoint, to some random person for review.  There is no approval, therefore I dont understand why I need to configure the approval action in the flow, I wouldn't want User A Manager to be confused about something needs to be approved.

Can you clarify the solution for non-approval flows? And what if User X leaves the company, do the flows fail?