{"id":110952,"date":"2018-05-21T07:07:17","date_gmt":"2018-05-21T14:07:17","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/share-with-sharepoint-office-365\/"},"modified":"2025-06-11T08:08:37","modified_gmt":"2025-06-11T15:08:37","slug":"share-with-sharepoint-office-365","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/share-with-sharepoint-office-365\/","title":{"rendered":"Share your Flows with Office 365 Groups and SharePoint Lists, Connector Updates, and Analytics with Error Details"},"content":{"rendered":"

This week, we\u2019re pleased to announce a host of new updates in Microsoft Flow from new sharing capabilities, major connector updates, and error analytics. Let us know what you think via the comments below and through our Community forums.<\/p>\n

Share your flows with Office 365 Groups and SharePoint lists<\/h2>\n

Currently Flow enables you to share flows with your colleagues either by adding them as co-owners or (for manual flows only) run-only users. As co-owners, they have full edit permissions for the flow. As run-only users of manual flows, they can only<\/em> run the flow. Till date, you could only add other individuals in your tenant or security groups. Today, we are enhancing these capabilities by allowing you to share all flows with Office 365 Groups<\/u><\/a> and for those flows that feature SharePoint triggers and actions with the referenced list or library.<\/p>\n

Share with Office 365 Groups<\/h3>\n

Suppose\u00a0you have a flow that\u00a0you want to share with an Office 365 Group called CRONUS Energy. From the Flow details screen,\u00a0you can choose to \u201cAdd another owner\u201d and simply enter the name or email address of the O365 Group. All members will be added as co-owners to the flow and can find it listed under Team flows.\u00a0\u00a0You can also add Office 365 Groups as run-only users to button flows.<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

Add a list as a co-owner<\/h3>\n

Let\u2019s suppose\u00a0you have a flow that runs when an item is created or modified in a SharePoint list \u2013 say Turbine Energy Distribution<\/em>, this flow also does a Get item from another list called Turbines<\/em>.\u00a0You can add both lists as co-owners to the flow so that everyone who has edit access to the list automatically gets edit access to the flow. Once the flow has been shared, you can simply distribute a link to it.<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

Add a list as run-only user<\/h3>\n

Similarly, let\u2019s suppose\u00a0you have a flow that sends out a document for approval and it references the Documents library. From the Flow details screen,\u00a0you can add the Site and corresponding Documents library as a run-only user, so that now all users that have read\/write\u00a0access to the Document library automatically have permissions to run the flow from the Flow menu in SharePoint.<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

SharePoint connector updates<\/h2>\n

As Flow is the successor to SharePoint Designer workflows, we continuously strive to improve our SharePoint connector capabilities. This week, we\u2019ve added two new capabilities \u2013 triggers for When an item or file is deleted and an action to Send an HTTP request to SharePoint.<\/p>\n

The new action helps advanced users that are familiar with the SharePoint REST APIs to build queries and get results from SharePoint, especially if existing actions don\u2019t currently support what you need or for scenarios where no action is available. For example, you can use this action to filter items using lookup fields or for controlling permissions to an individual item.<\/p>\n

\"\"<\/p>\n

Two new connectors<\/h2>\n

Last week we also released two new connectors in Microsoft Flow:<\/p>\n