Sharing Flows in "Solutions"

[ShaunW]

I’m having trouble with having the buttons show up on a run-only user’s mobile device.

The buttons DO show up if I share one of “my flows” but DON’T if the flow is part of a “solution”.

My goal is to create parent and child flows (thus I require them to be part of an environment / solution) to prevent users from seeing the logic / information in the child flows.

Are there any resources / documentation / blogs anyone can point me towards? Does anyone have any advice or has experienced this issue?

Any help you can provide would be appreciated.

Shaun

[ChristianAbata]

hi @ShaunW  in my experience you need to share your flow. We can't hide our flow config if you share your flow.

[ShaunW]

@ChristianAbata Thank you for your help. I did share my flow.

The flow is a manual flow created in a solution. I added a new run-only user. The button doesn't show up on the mobile app.

Thoughts?

[ChristianAbata]

mmm @ShaunW is weird... I try to log in and log of from the app mobile, because if you share your flow of course he is going to see the button of course when is manual flow..

[ShaunW]

@ChristianAbata I logged-out and logged back in. Still doesn't work.

When I share a flow that is located in "My Flows" -- this works.

When I share a flow that is located in "Solutions" -- this doesn't work.

Shaun

[ChristianAbata]

oh @ShaunW  to show your button the flow needs to be in My flows.

[ShaunW]

I see.

Ok, so how do I run a flow that's part of a solution but use the connections of the user that triggered the flow?

The flow was built using my connections. If they run it, they'll use my connections. I want them to use their connections.

[abm]

Hi @ShaunW 

What type of connectors are you using in your flow?

Thanks

[Panoone]

@ShaunW , if you just wat them to run the flow then you simply need to be sure those users have access to the environment. The same goes for the target environment when deploying your solution from DEV, UAT to PROD.

If the environments are secured with an access group, simply add the users to the relevant group.

To share ownership of the Flow, you unfortunately need to explicitly add each user. This is a major flaw in the implementation of the security model. If only it followed the same rules as model-driven apps.

Power Platform can, of course, gain access to the flow on-demand.