cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
alexander75671
Regular Visitor

Using Flow as a group

I have been using flow for a while to automate some processes we have here at work - mainly with SharePoint Online, but with a few other things here and there. One thing I am unsure about is how should I set this up to outlive me at my job?

 

Currently, I have created a service account at work that is a SharePoint admin, email box, etc. The Service Account is licensced and we all login to it to edit our flows. The idea is that everyone has access to the flows, it outlives us, and is always avaliable for anyone to edit and own in our group. Most of our flows are basically just sending an email when a SharePoint item is created with all the details to certain distros and users.

 

I cannot seem to find a way around this. I know there is Team Flows, but every time someone makes an edit to the flow, everyone gets emailed. Also permissions is still a little weird in this case where technically the person that creates it is the only owner and everyone else can just edit.

 

How can I update this where we do not have to login to Flow as a service account and edit under one user? I want to be able to share flows, everyone own flows, flows not tied to any user, etc.

1 ACCEPTED SOLUTION

Accepted Solutions
Pstork1
Dual Super User
Dual Super User

If you want to guarantee that a Flow continues to run without intervention when someone leaves the company, then the solution you are currently using is really the only option. Most Flows, other than Flows started manually with a button, always run in the context of the original maker. There is no way to create a Flow that isn't associated with an individual.  So building Flows as a service account is your best option.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

2 REPLIES 2
Pstork1
Dual Super User
Dual Super User

If you want to guarantee that a Flow continues to run without intervention when someone leaves the company, then the solution you are currently using is really the only option. Most Flows, other than Flows started manually with a button, always run in the context of the original maker. There is no way to create a Flow that isn't associated with an individual.  So building Flows as a service account is your best option.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Seems like there should be a feature for this, so Flow is for sure lacking in that department, but thanks for your answer. I was afraid of that.

Helpful resources

Announcements
Microsoft 365 Conference – December 6-8, 2022

Microsoft 365 Conference – December 6-8, 2022

Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.

Users online (4,975)