Forum Discussion
MicrosoftIntroducing "Request sign-off" - an approval flow that requires no set up
You really have put the cart before the horse by implementing functionality like this before providing any way to manage it. I can't have users going off and running flows you have arbitrarily created and pushed out to my lists without giving me any control. This whole flow thing is half-baked unless you have an IT staff that can devote time to keep it under control. And I don't have any IT staff. For the most part Flow is creating more problems than it is solving simply because the rollout is not being managed well by Microsoft.
At last, a sensible position on the introduction of new features to end users. It can be seen from many posts on this thread that the solution is effectively a "beta". Some very good posts here with regard to "real life" issues around permissions, the ability to edit the control field etc.
Now, whilst it is commendable that Kerem is taking on board these suggestions (and it seems he is very good at taking a suggestion and implementing it), the introduction of these types of features are a veritable nightmare for the support teams. It really does not help when half developed add-ons become visible to end users who a) quickly adopt them b) find out scenarios to break them then c) demand that IT department to fix them.
I would kindly suggest that the philosophy of immediately turning "ON" these features for end usrs should be revisited.
By all means introduce them but please add them in with the default of being turned "OFF".
Then allow only a certain role (say Full Access) to have the ability to turn them "ON".