Approvals Flow

[IanR]

Hi all So i have built and approval where the user goes to PowerApps and submits the approval from

The form updates a SharePoint list and triggers the approval to 3 individuals (first one to respond)

However what i am seeing is this

All approvals , no matter who submits them, come from my name (i understand there is no work around for this)

But what is the main issue is once the item is approved or rejected all those notifications come back to in Teams. Is there anyway to stop this?

[Pstork1 · Accepted solution]

The approvals all run as you because you are using an automated trigger on the flow.  Automated flows always run in the context of the maker of the flow.  That's why the modification to the item is in your name.  If you change the trigger to a manual one and start the flow from the Power Apps form on a button the flow will run in the context of the user who pressed the button.

You can managed the Approval notification settings just like any other notification in Teams.  Go to the gear menu, select Notifications and scroll down till you see Approvals. Click on that button to edit the notification settings.

[IanR]

great idea thanks

[IanR]

I've been trying to trigger this flow manually with the button in PowerApss but unsuccessful, would you have a starting example of how to achieve this?

Thanks

[Pstork1]

To call the flow from a button in Power Apps you'll need to change the trigger to a Power Apps trigger.

Here's a video.

PowerApps call Power Automate flow with parameters - YouTube

[IanR]

Thanks, I successfully set it up but ran into another snag 🙂

Powerapss now is the trigger via Button

the flow works but once the approval was given an email was sent using "send as" credentials (which i have) But now i'm using the PowerApps as the trigger the email fails as user doesn't have permission (i assume it is trying to send the email using the submitters permission) Is there a way to force it to use mine? just for the email

[Pstork1]

The email will be sent using the security context of the person who pressed the button.  Just as the approvals now run in the context of the user who pressed the button.  There is no way to change that other than using the automated trigger as you originally did.