Creating useful "bots" and flows is extremely limited when they are all tied to the user which created them. Many times, the users which create them are either contractors or IT professionals which are not the ones which will actually be benefiting from the process automation. The flow needs to have an option to "Run As the Initiator" vs "Run as the Owner."
Another great benefit of this is that (for example) the flow can be made available for an entire sharepoint site or MS Teams channel, but only those with permissions (for example to modify a list item) would be able to successfully execute the Flow. For a MS Teams channel, a flow running as the initiator could serve actions for the user from resources only that user can access, such as adding a reminder to their calendar.
If the flow is started manually using a Button on Mobile or a Power Apps Button it will run in the context of the user who presses the button. But if a flow is automatically started by a trigger then it will run in the context of the original maker.
User | Count |
---|---|
88 | |
40 | |
23 | |
20 | |
16 |
User | Count |
---|---|
128 | |
48 | |
46 | |
27 | |
26 |