cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AMH08
Advocate I
Advocate I

Approval Process Requested By

We have a centralized flow account to manage some business Flows. 

 

I find myself tinkering with an approval flow. The approval is working. However, the approval always says it is being requested by the account the flow lives on. Is there a way to configure that to be someone else without the flow living on that someone else's account? 


What I would like to do is have the requested by be whoever was entered in a person field within the sharepoint list item that was triggered by the flow. 

 

The only options I see for the approval is:

Title, Assigned To, Details, Item Link, Item Link Description. 

29 REPLIES 29
v-xida-msft
Community Support
Community Support

Hi @AMH08,

 

Do you want to change the requestor (Requested by) of the Approval email sent through "Start an approval" action dynamically?

 

The requestor (Requested by) of the approval email sent through "Start an approval" action is based on your current login account of Microsoft Flow. In other words, if you login in Microsoft Flow with the account of user A, the requestor (Requested by) of the approval email sent through "Start an approval" action is user A, if you login in Microsoft Flow with the account of user B, the requestor (Requested by) of the approval email sent through "Start an approval" action is user B.

 

There is no way to change the requestor (Requested by) of the Approval email sent through "Start an approval" action dynamically in Microsoft Flow currently, if you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Best regards,

Kris

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Kris - I createrd a Flow idea per your instructions. This seems like a faulty design to hard code an approval request to show as coming from the person who created the flow. Approvers (managers or otherwise) do not need to know, nor would they care, who created the Approval Flow. This could often be an IT resource. Approvers would primarily be concerned with who created the item requiring approval.

 

I can think of a use case where this hard coding of the Flow creator makes sense for an approval. 

 

Nigel1
Advocate I
Advocate I

The Approval flow email needs to have an option to show who the Approval Request has orginated from rather than showing the default name of who created the flow.

Gristy
Resident Rockstar
Resident Rockstar

Hello,

The approval email comes from a microsoft.com address you cannot change that.

 

What you can do is insert your people value into the Requestor field in the approval like this, click show advanced options

 

Annotation 2019-10-03 150159.png

The problem isn't the ability to add a "Requestor" merge field into the body of the approval email, it's that the Flow Owner is featured prominently in the first line of the approval request email and is prefaced by "Requested by". In fact, the physical person requesting approval for an item is listed below that. 

 

Therefore, the problem is two-fold in my observation:

  1. The inappropriate hard coding of the phrase "Requested by" to identify the Flow Owner but is not requesting approval for anything. 
  2. The order of the email and inability to edit/move/hide the hard coded pieces. The request originator should be featured more prominently because they are the one actually requesting approval of a thing. They are the one who created the new list/library item, not the flow creator. Most times the flow creator is an IT staff member or the "tech person" on a team, who couldn't care less about the daily approvals occuring on the list itself. 

 

approval.png

 

ITCowboy
Advocate I
Advocate I

I agree, this is not very well thought out. I am the IT person at or company, and also the only one with time and knowledge to create these flows. No-one cares that I created the flow. 

 

Example, I am using an approval list for vacation requests. The user puts in their information (dates, times, etc), managers name, and it kicks off the email to be approved or rejected. 

 

The manager receives an email, which shows all that information, but prominently at the top, the mail shows my picture, and "Requested by MY NAME", followed by my email address. 

 

That line is there because I created a flow for others to use, but I keep getting calls asking why I am requesting vacation from them (they are not my manager). It is confusing to the workflow process, and completely unnecessary to show any information about me in this instance, or most others I can think of.

 

The company wants to use sharepoint Online,  as we have been using with an inhouse version for years, but it seems the technology has moved backwards, and is not ready for prime time use yet. I cant do many things that I was able to do with SharePoint designer easily before.

 

If anyone hears or finds a fix for this, Please, let us know!

Anonymous
Not applicable

Also facing the same problem.

 

If the "Requested By: FLOW_OWNER" text simply didn't exist this wouldn't be an issue. If someone requests holiday time by updating a Sharepoint list then whoever gets the approval email does not care about who created the flow. The only info they need is the name of the person who created the list item.

 

This is a major flaw and surely a simple fix.

There is already a field you can change who the requestor is in advanced settings.

Anonymous
Not applicable

How can you change who appears as the requestor? I don't see any field for it in Flow. Where are the advanced settings you're talking about?

Anonymous
Not applicable

This is what I see in flowThis is what I see in flow

 

I see no option for advanced settings.

Hi,

 

It is here and also in start and wait for an approval.

 

it looks like maybe you are using old/deprecated action.

 

Annotation 2019-11-12 215327.png

Anonymous
Not applicable

Thanks for your help and the fast reponse.

OK, better, I did find the newer version that allows the requestor field.. Problem is, Microsoft should not be automatically fielding any of that information. the new version shows requested by: (requestor), and created by: (Myself) now, neither of which do I want to show. I can and do include that information in the body or subject line for the flow in a friendlier more readable format for any flow, if that information is needed, using Dynamic Content. 

 

I get that information is used in the flow itself to make it work, there is just absolutely no reason that information should be provided automatically, especially in this case where there are other means to show that information if wanted. If it must be there, at least it should be in small lettering at the bottom of the email, where my users will not read it, or misconstrue its meaning. My name has no need to be on any communication, post, or end result that user initiated in a flow, unless I am the one initiating that flow for its intended purpose. 

Anonymous
Not applicable

Hello, I stumbled upon this thread as I was sending same request for help. I thought it had to do with SharePoint Permission. I have spend weeks and Months learning Power automate and I need to demonstrate my effort to my department, only to realize that in our testing before the demonstration, my e-mail address is showing in the Requested By and not the actual actual item creators? This is not the kind of development that will be acceptable in my organization. For the time being is there no way i can eliminate my e-mail address from the creator? Yes i created the flow but nobody needs to see that every time, its defeats the purpose and I agree with everyone against this flaw Thank you

I do have the same issue, is the issue fixed? can someone please help me on this

jrauca
Regular Visitor

Still no response from microsoft. Is there any reason why the creator of the flow needs to be tagged?

any update on this? Seems still there's no fix for this.

I don't understand why, when you have no entry in the "advanced" Requester field, there's only the PA creator listed in the email. But as soon as you fill out the advanced field with an email address of the "list created by:" we suddenly need to add a new section, with different, complete unreasonable/confusing information that must be the creator of the workflow (and don't allow it to be removed.) Come on, man! Really?!?!

PS Even this post/topic was hard to find and it only half works. (*shaking-head-in-dismay*) 

THIS SHOULD BE LISTING IN THE KNOWN LIMITATIONS AT A MINIMUM!

draxler669
New Member

I have the same issue and I cannot find an advanced settings for the approval ive got. therefore I have not way to remove the requestor email (the flow creator)!

draxler669_0-1623821940808.png

 

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (6,060)