I'm a bit curious about the general consensus on this topic.
I'm creating flows under my own user.
Some flows are accessible for the whole organisation through various triggers.
I'm noticing that approvals, for instance, are always sent out by me, which isn't always logical in the context.
Is it considered good practice to set up a separate user account, that "owns" the flows? That way it's possible to differentiate between what content actually comes from me and what has been created by an automatic trigger.
Or do you think it is fine that the admin shows up as owner/sender of certain content?
@mahoneypat Thanks Pat.
So, just to spell it out, you have a separate service account, which then owns the flows.
You log in as this account to create and edit flows or otherwise do general maintenance?
Sorry if these questions are a bit dim, but this type of automation is new to me. Usually I would have a server running all automations, so this cloud based stuff seems a tad confusing with the ownership and I'm finding it hard to look up any good documentation on the subject.
Yes. It is a common practice to set up a service account for these scenarios.
Pat
WarrenBelz
146,537
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,908
Most Valuable Professional