Prevent non-uploader of starting a workflow

(0) Share

Report

Posted on by DJanssen

427

Hello,

I was wondering if the following requirement is possible. I have a Sharepoint Document Library where users can upload their documents and submit it for approval. However it seems that if user A uploads a document, user B can press on the button to start the workflow.

I was thinking of implementing the following:

After the get File Properties action that comes after the trigger I want to create a condition that checks if the CreatedBy Email with a field that could determine which user triggered the flow. Does somebody know which action to use?

But ideally I would like to catch this behaviour in the Sharepoint Document Library. Is there any way to do this outside of the Power Automate workflow?

Thanks in advance 🙂

I have the same question (0)

All responses (3)

Answers (1)

Pstork1 68,306 Most Valuable Professional on at

Like (1)

Report
Re: Prevent non-uploader of starting a workflow

This wouldn't be outside the flow, but you could try adding a trigger condition to the flow trigger that prevents it from firing if the person triggering the flow isn't the author. the trigger condition would look something like this

@equals(triggerOutputs()['headers']['x-ms-user-email-encoded'], 'triggerBody()['Editor']['Email']')

Was this reply helpful? Yes No
DJanssen 427 on at

Like (0)

Report

Re: Prevent non-uploader of starting a workflow

Hi @Pstork1 ,
Thanks for the reply this is nice food for thoughts! Do you perhaps also know if it's possible to compare those values in the if condition? I could then notify the user who clicked on the button that this document was not meant to send for him/her.

I'll discuss with my client what is preferred; a non responsive button or a notification.

Was this reply helpful? Yes No
Verified answer

Pstork1 68,306 Most Valuable Professional on at

Like (1)

Report

Re: Prevent non-uploader of starting a workflow

Yes, you should be able to do that in a condition action inside the flow. Its just comparing two values available in the trigger.

Was this reply helpful? Yes No