Is there a way to share Flows?
For Corporate it's not good to assign flow to single user. It would be great to make flows for group of people to monitor and maintain Flow
This is now available in preview! See here for more details: https://ms.flow.microsoft.com/en-us/blog/team-flows/
Thank YOU!!! You have saved me few extra hours per week!
Now i can share flows with my coleagues!
Feature is not fully finished, have some bugs at connections after sharing, so half of shared flow connections must be recreated
You are going right way!
We are very excited to have released this feature ! Please let us know if you have feedback around Team Flows and what features you would like us to add in this space.
Links to documentation : https://flow.microsoft.com/en-us/documentation/create-team-flows
I just tried using Flows to work with Teams. (I want SharePoint library publish/approve workflows that don't use email for notifications). I had hoped that the team flows would be usable, but unfortunately hit a few problems. I have been able to implement a 'notify team for review' flow, but cannot make it work how I want without having every team member create their own flow. These are the main issues so far:
1. The account stays with the flow definition - I want it to run as the (federated) account of the person launching the flow.
2. I want to allow all the team to use the flow, but only one or two people allowed to edit it
3. I can't find a way of hooking the major/minor sharepoint library publishing status into the flow
4. I want to be able to include @person references in the Teams post
I appreciate that it's early days yet, and I am encouraged by the direction here, but using Flow to more tightly integrate SharePoint and Teams is a high priority for me now.
I second ChrisE's comment: Flows needs more levels of control and to run in the user's context.
I've made a 'When email arrives, do something', and I ideallly want multiple to use it. But as of right now, I have only one option, which is to have everyone duplicate the Flow and add connectors to their own email.
Which simply won't work, because if I need to update the flow, each copy for each user needs to either be updated or replaced.
Secondly, we need more tiers of shared rights, as ChrisE again mentioned. I want to share with people who can: own/edit, read/run, run-only. The latter case would allow hiding of sensitive API keys for HTTP connectors from all users.