Power Automate

Manage run-only permissions - general questions

(0) Share

Report

Posted on by SigiS70

Can anyone provide me some hints/infos about the effects of the "manage run-only permissions"?

For child flows "run-only-users" were not working, wo i am using my own connection.

So far so good.

Additionally I have to share the flow with "user and groups" or "sharepoint".

1.) If I'm entering both "users" and "sharepoint" is this complementary?

2.) Or is that not recommended?

3.) On "Sharepoint" counts that for every user of the list/library regardless if they have only view permissions?

Many thx,

Sigi

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

David_MA 12,982 Super User 2025 Season 2 on at

Like (0)

Report

To answer your question depends on the trigger and what your flow is doing. Please share a screen shot of your flow. Child flows only work if you have your flows within a solution which requires an environment with Dataverse enabled.

You can also review this for details about owners and run only permissions: Manage owners and users in your Microsoft list flows with Power Automate | Microsoft Learn

Was this reply helpful? Yes No
Suggested answer

SigiS70 13 on at

Like (0)

Report

Thx for your reply, like mentioned it's a general questions not specific for one flow.

The trigger for child flows is afaik all the time "trigger manual" and let's assume there is only the action "respond to powerapps".

Thanks for the link it answers my question #3: it's only for users with edit permissions.

So i come to the conclusion that the settings in "user and groups" and "sharepoint" are additional.

The difference is that "users" have only run abilities and "sharepoint" the flow is shared therefore also editable.

Was this reply helpful? Yes No
Suggested answer

David_MA 12,982 Super User 2025 Season 2 on at

Like (0)

Report
To answer your question in a general sense, how you configure the run only permissions depend on the flow and the action. For example, if you are sending an e-mail, you probably want that action to run on the credentials of the person who initiates the flow. However, if you need to populate a Word template that is stored in the OneDrive of the owner of the flow, you will want that action to run on the account of the flow owner so it can access the template. Here is a bit more detail:

When to Run Actions on the Flow Owner's Account:

Access to Specific Resources: If the action requires access to resources that are only available to the flow owner, such as files stored in the flow owner's OneDrive or SharePoint, you should run the action on the flow owner's account. This ensures the action has the necessary permissions to access and manipulate those resources.

Consistency and Control: When you need to maintain consistent behavior and control over the action, regardless of who triggers the flow. For example, if you have a standardized template or a specific email format that should always be used, running the action on the flow owner's account ensures it is executed uniformly.

When to Run Actions on the Triggering User's Account:

User-Specific Data: If the action involves data or resources specific to the user who triggers the flow, such as sending an email from their account or accessing their personal files, you should run the action on the triggering user's account. This ensures the action is performed in the context of the user and respects their permissions and data.

Personalization: When the action needs to be personalized based on the user who initiates the flow. For instance, if the flow sends a notification or an email, running it on the triggering user's account allows the message to come from their email address, making it more personal and relevant.

By choosing the appropriate account for each action, you can ensure that your flow operates smoothly and securely, leveraging the correct permissions and context for each task.

Was this reply helpful? Yes No