#Flow – Support for Team coauthoring, and sharing

Hello!

A couple of days ago, the Microsoft Flow Team announced a very interesting feature: “Teams Flows”. So, now when we create or edit a Flow have the option to share it with other users or groups of users. As a sample, let’s look the next picture, we have a new action “Teams” for each one of the Flows in the Flows list.

clipboard03

We can add new people with a Owner role. This allows them to edit and collaborate in the Flow definition. In addition they are going to be able to see the log executions of the flow.

clipboard05

I guess here it would be ideal to have a new role for a group which can only see the execution of the Flows but they will not be allowed to edit them.

Moving to edition for teams, there are some important things to keep in mind. Let’s suppose that I created a Flow and I use a Sharepoint connection to a repository, and in a further action I need to interact with Dynamics CRM information. But my account does not have permissions for this action. At this point, I invite to collaborate to a person with permissions, and that person can use his/her credentials to create the CRM connection. At this time the Flow uses 2 different user accounts to 2 different actions. The important thing to note here, is that every single editor can use and modify the connections that are associated with your account. In this way, a new range of possibilities where people opens with different roles can create more complex and collaborative Flows.

Finally, this feature is available for the pay version of MS Flow.

Greetings @ Vancouver

El Bruno

References

42 comments

  1. Pingback: #Flow – Creando Flows basados en una agenda – El Bruno
  2. Pingback: #Flow – Schedule a Flow execution, recurrence supported! – El Bruno
  3. Pingback: #Flow – HowTo recorrer colecciones de elementos (#Excel, #Sharepoint, y más …) – El Bruno
  4. Pingback: #Flow – How To iterate through collections of elements (#Excel, #Sharepoint, and more…) – El Bruno
  5. Pingback: #Flow – “Guardar como” e integración con botones reales: Flic y Bttn – El Bruno
  6. Pingback: #Flow – “Save as ” and interaction with physical buttons: #Flic and #Bttn – El Bruno
  7. Pingback: #Flow – Ahora con soporte para #ComputerVision #CognitiveServices – El Bruno
  8. Pingback: #Flow – New action definition to use #ComputerVision operations. #CognitiveServices – El Bruno
  9. Pingback: #Flow – Buttons Widgets para iOS y Android – El Bruno
  10. Pingback: #Flow – Buttons Widgets in iOS and Android – El Bruno
  11. Pingback: #Flow – Gestionando excepciones o errores en un Flow – El Bruno
  12. Pingback: #Flow – Manage errors, exceptions, timeouts and more on a Flow definition – El Bruno
  13. Pingback: #Flow – Manejo simple de variables en Microsoft Flow – El Bruno
  14. Pingback: #Flow – Working with variables in #MicrosoftFlow – El Bruno
  15. Pingback: #Flow – Opciones avanzadas en HTTP Action con #MicrosoftFlow, Headers, Authentication y más ! – El Bruno
  16. Pingback: #Flow – Advanced options to work with HTTP Actions in #MicrosoftFlow, Headers, Authentication and more! – El Bruno
  17. Pingback: #Flow – HowTo lanzar un Button Flow desde un navegador – El Bruno
  18. Pingback: #Flow – How To emulate a Button for a Flow using a Browser – El Bruno
  19. Pingback: #Flow – Exportar e Importar definiciones de Flow con algunas opciones avanzadas – El Bruno
  20. Pingback: #Flow – Export and Import Flow definitions with advanced options – El Bruno
  21. Pingback: #Flow – Trabajando con expresiones (esto sube la productividad un 50% !) – El Bruno
  22. Pingback: #Flow – Working with expressions (50% more of power!) – El Bruno
  23. Pingback: #Flow – Nuevas opciones en Flow Button con listas de opciones como datos de entrada – El Bruno
  24. Pingback: #Flow – New input options when using Flow Button: list of choices – El Bruno
  25. Pingback: #Flow – Comenzar un Flow asociado a un elemento en una lista de #Sharepoint – El Bruno
  26. Pingback: #Flow – Trigger a Flow associated to an item in a #SharePoint list – El Bruno
  27. Pingback: #Flow – Controla el estado de tus Apps en #Azure Con #ApplicationInsights y #MSFlow – El Bruno
  28. Pingback: #Flow – Check your Apps health in #Azure using #ApplicationInsights and MSFlow – El Bruno
  29. Pingback: #LogicApps – Intro y diferencias con Microsoft Flow #MSFlow – El Bruno
  30. Pingback: #LogicApps – Introduction and main differences with Microsoft Flow #MSFlow – El Bruno
  31. Pingback: #LogicApps – Creando nuestra primera Logic App en #Azure – El Bruno
  32. Pingback: #LogicApps – Let’s create our first Logic App in #Azure – El Bruno
  33. Pingback: #LogicApps – Trabajando con Visual Studio 2017 y LogicApps #VS2017 – El Bruno
  34. Pingback: #LogicApps – Working with Visual Studio 2017 and Logic Apps #VS2017 – El Bruno
  35. Pingback: #Flow – Manejando información de configuración de Apps con #OneDrive, #Excel, Microsoft Flow y peticiones HTTP – El Bruno
  36. Pingback: #Flow – Using configuration information from an App using #OneDrive, #Excel, Microsoft Flow and HTTP Requests – El Bruno
  37. Pingback: #Flow – Analizando imágenes en 3 pasos con Microsoft Flow y Computer Vision #CognitiveServices – El Bruno
  38. Pingback: #Flow – Analyzing images in 3 steps with Microsoft Flow and Computer Vision #CognitiveServices – El Bruno
  39. Pingback: #Flow – Reasignado una tarea de aprobación – El Bruno
  40. Pingback: #Flow – New feature: Approval reassignment – El Bruno
  41. Pingback: #Flow – Analizando imágenes en Listas de #Sharepoint utilizando #CognitiveServices – El Bruno
  42. Pingback: #Flow –Analyzing images in #Sharepoint Lists using #CognitiveServices – El Bruno

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.